On Fri, Aug 13, 2010 at 1:17 PM, Nick Mathewson <ni...@freehaven.net> wrote: > On Thu, Aug 12, 2010 at 2:31 AM, Avi Bab <a...@trustwave.com> 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 solution > than moving current_event_lock from being a lock to being a condition > or something. More thought is probably needed, though. :/
With help from Chris Davis, I've got some patches committed to master that stand an okay chance of solving this issue. It would be neat if somebody has a chance to test them out before we release 2.0.7-rc. yrs, -- Nick *********************************************************************** To unsubscribe, send an e-mail to majord...@freehaven.net with unsubscribe libevent-users in the body.
