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

On Sun, May 29, 2011 at 9:25 PM, Nick Mathewson wrote: [...] > Below is a short program I tried to use to reproduce this, but > valgrind didn't tell me about any reads of uninitialized memory.  Does > purify complain about the program below? > And here's a simpler program to check whether purify

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

On Sun, May 29, 2011 at 8:27 PM, Scott Dorr wrote: > Purify complains about Unitialized Memory Reads when I try to push more than > 64 events onto the queue at the same time.  This is in a 64bit application > running on RHEL linux.  I'm currently using libevent-2.0.10-stable. > epoll_dispatch trig

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

Purify complains about Unitialized Memory Reads when I try to push more than 64 events onto the queue at the same time. This is in a 64bit application running on RHEL linux. I'm currently using libevent-2.0.10-stable. epoll_dispatch triggers a set of of 4 UMRs for each event past the 64th that I