On Sat, Jun 14, 2008 at 11:13 AM, Nick Mathewson <[EMAIL PROTECTED]> wrote: > In other words, something fishy is afoot here. Having a stack trace > and the contents of the offending struct event might help track it down.
To me this seems like some kind of memory corruption might be happening; such as accessing an event that was freed or creating an event on the stack that becomes invalid when the function returns. Niels. _______________________________________________ Libevent-users mailing list Libevent-users@monkey.org http://monkeymail.org/mailman/listinfo/libevent-users
