Afraid I'm going to have to eat my words here, Nick. It looks like something is
going on in the code - not entirely sure just where yet (mine or libevent).
I've installed a clean version of 2.0.13 (removing everything but the glue)
into OMPI, and the problems persist. I've also tried converting
On Jan 6, 2012, at 7:02 AM, Nick Mathewson wrote:
> On Fri, Jan 6, 2012 at 7:24 AM, Ralph Castain wrote:
>> If it helps, I have now confirmed that I *can* activate the t2 event during
>> the t1func callback in my example *provided* I called event_assign on it
>> prior to entering event_base_lo
On Fri, Jan 6, 2012 at 7:24 AM, Ralph Castain wrote:
> If it helps, I have now confirmed that I *can* activate the t2 event during
> the t1func callback in my example *provided* I called event_assign on it
> prior to entering event_base_loop. It is also okay for me to event_add the t2
> event d
If it helps, I have now confirmed that I *can* activate the t2 event during the
t1func callback in my example *provided* I called event_assign on it prior to
entering event_base_loop. It is also okay for me to event_add the t2 event
during the callback - I am simply not allowed to event_assign *
I've pursued this further, and now I am wondering if this is a libevent issue -
or perhaps I'm misusing the library. The cause of the segfault appears to be
the activation of the event created during the event callback. If I delay
activation so it occurs outside of the callback, then everything
