It's no big issue, I was just wondering if this was in my usage or it's generic libevent.
I have some programs which get tested under valgrind, and valgrind complains about libevent, so maybe a global event_library_cleanup() would be enough. I don't have enough knowledge of the internals, but if anyone would be interested in reviewing such piece of code, I think I can get it done. I suppose it's just adding free functions for any module (evsig, secure_rng) and calling them from the global free. Andrei On Mon, Jul 11, 2011 at 6:20 PM, Mark Ellzey <mtho...@strcpy.net> wrote: > Ah, this is a global lock. > > Unfortunately there doesn't seem to be a way to free that, is it a big > issue? this is small, one time allocat, and handled by dtor's. > > *********************************************************************** > To unsubscribe, send an e-mail to majord...@freehaven.net with > unsubscribe libevent-users in the body. > -- Mobile: +49 151 42647382 e-Mail: andre...@gmail.com
