Re: [Libevent-users] deadlock in version 2.0.5

2010-08-17 Thread Nick Mathewson
On Fri, Aug 13, 2010 at 1:17 PM, Nick Mathewson wrote: > On Thu, Aug 12, 2010 at 2:31 AM, Avi Bab wrote: >> The scenario – > > Ick.  I've added this one to the bugtracker as > https://sourceforge.net/tracker/index.php?func=detail&aid=3044479&group_id=50884&atid=461322 > ; further discussion there

Re: [Libevent-users] deadlock in version 2.0.5

2010-08-13 Thread Nick Mathewson
On Thu, Aug 12, 2010 at 2:31 AM, Avi Bab wrote: > The scenario – Ick. I've added this one to the bugtracker as https://sourceforge.net/tracker/index.php?func=detail&aid=3044479&group_id=50884&atid=461322 ; further discussion there. >From what I can see now, there doesn't seem to be a better sol

[Libevent-users] deadlock in version 2.0.5

2010-08-11 Thread Avi Bab
The scenario – Thread B tries to delete an event E for which a callback is executed by thread A. The callback calls event_base_gettimeofday_cached() that acquires th_base_lock: Thread A (LWP 14625 in the stack/strace below) locks *current_event_lock* before invokoing callback. Thread B (LWP