On Sat, May 07, 2016 at 02:08:35PM +0530, vijay mishra wrote: > Dear All, > > In attempt to fix this problem, we ported the latest libevent beta release > (2-1-15, beta release) and with that , this issue is resolved but we are
Hi, I guess you meant *2.1.5*? > not able to find which exact commit in the latest libevent might be solving > this issue > > Can anyone here help us identify the commit which may have had this issue > fixed. > > PS: in stable release version 2-0-22,the issue was seen. So we suspect some > commit after that is fixing this issue. There are a lot of changes between 2.0.22 and 2.1.5, and I'm not even sure because of which layer this can be, maybe you can do some bisecting? Thanks, Azat. *********************************************************************** To unsubscribe, send an e-mail to [email protected] with unsubscribe libevent-users in the body.
