Re: [Libevent-users] Unitialized Memory Read when pushing >64 events at once

2011-06-04 Thread Adrian Chadd
On Sat, Jun 04, 2011, Nick Mathewson wrote: > On Sat, Jun 4, 2011 at 2:14 PM, Scott Dorr wrote: > > Sorry I didn't get a chance to fiddle with this until just now. ?The short > > program below does generate uninitialized memory reads when executing the > > printf(). ?If I add a memset() right afte

[Libevent-users] ANN: Libevent-2.0.12-stable is released

2011-06-04 Thread Nick Mathewson
Hello, all! Announcing Libevent 2.0.12-stable = Libevent 2.0.12-stable is now tagged and released. The package is at Sourceforge at: https://sourceforge.net/projects/levent/files/libevent/libevent-2.0/libevent-2.0.12-stable.tar.gz/download and the signature f

Re: [Libevent-users] Unitialized Memory Read when pushing >64 events at once

2011-06-04 Thread Nick Mathewson
On Sat, Jun 4, 2011 at 2:14 PM, Scott Dorr wrote: > Sorry I didn't get a chance to fiddle with this until just now.  The short > program below does generate uninitialized memory reads when executing the > printf().  If I add a memset() right after the events[200] declaration > (before the epoll_wa

Re: [Libevent-users] Unitialized Memory Read when pushing >64 events at once

2011-06-04 Thread Scott Dorr
Sorry I didn't get a chance to fiddle with this until just now. The short program below does generate uninitialized memory reads when executing the printf(). If I add a memset() right after the events[200] declaration (before the epoll_wait() call), the uninitialized memory issue goes away, thoug