Nick, I have made my code capable of running multiple sets of single-threaded SSL bufferevent+event_base (i.e. works with current libevent 2.0) as well as able to run fully multithreaded (breaks with current libevent 2.0) I will be happy to test the changes in my real softwarewhich would probably be a better stress test than the simple test software I posted before.
Thanks, -John ________________________________ From: Nick Mathewson <ni...@freehaven.net> To: libevent-us...@freehaven.net; John <jjchnk-libev...@yahoo.com> Sent: Thursday, April 25, 2013 11:36 AM Subject: Re: [Libevent-users] Simple question about multithreading SSL bufferevents. On Tue, Mar 26, 2013 at 6:32 PM, John <jjchnk-libev...@yahoo.com> wrote: > Hello all, > > I am having significant issues with (near immediate) deadlock when trying to > send data out a single openssl bufferevent from two separate threads. FWIW, I can confirm that my current "21_deadlock_fix" branch makes your example code run as expected. See the thread "RFC: strategy for deadlock avoidance and safe finalization in Libevent 2.1" from earlier this month for more information on that. I hope to clean it up in the next few days and merge it soon. Ideally, I would like to get the next Libevent 2.1.x-alpha released over this weekend. best wishes, -- Nick *********************************************************************** To unsubscribe, send an e-mail to majord...@freehaven.net with unsubscribe libevent-users in the body. *********************************************************************** To unsubscribe, send an e-mail to majord...@freehaven.net with unsubscribe libevent-users in the body.
