[Libevent-users] libevent custom thread library: Recursive mutexes and wait conditions

Hello libevent, I am writing to see if I could get clarification on wait conditions and their use with recursive locks. My first issue is understanding how a custom evthread_lock is supposed to be implemented. evthread_lock_callbacks::supported_locktypes() documentations says "Note that RECURSIV

[Libevent-users] Callback after all events from the current batch have been cleared

I'm looking at a bug which appears to come down to: some of my event callbacks deallocate events, bufferevents, and/or their callback data. Under difficult-to-reproduce circumstances, libevent appears to queue up calls to my callbacks (possibly implicitly via internal control flow), and call th

Re: [Libevent-users] Assertion fails in insert_common_timeout_inorder

On Mon, Jun 25, 2012 at 2:41 AM, Avi Bab wrote: > > > > > I am using libevent-2.0.18-stable running on Liux (CentOs 6.2). > > Adding an event with a common timeout I get an assertion failure in > insert_common_timeout_inorder (event.c:2532): > “EVUTIL_ASSERT(is_same_common_timeout(&e->ev_timeout,