It gives me great pleasure to be able to carp about the following warning from valgrind:
==19138== Syscall param kevent(changelist) points to uninitialised byte(s) ==19138== at 0x24AD906: kevent (in /usr/lib/libSystem.B.dylib) ==19138== by 0x31274F: event_base_new (event.c:197) ... ==19138== Address 0x8e044c8 is 8 bytes inside a block of size 1,280 alloc'd ==19138== at 0x1067D63: malloc (vg_replace_malloc.c:193) ==19138== by 0x316162: kq_init (kqueue.c:123) ==19138== by 0x31274F: event_base_new (event.c:197) ... This was with a copy of valgrind built from the DARWIN branch, co svn://svn.valgrind.org/valgrind/branches/DARWIN cd DARWIN sh autogen.sh make -j2 sudo make install and the following xcode settings when building the test app: Debug Information Format -> DWARF with dSYM file Strip Debug Symbols During Copy: uncheck Strip Linked Product: uncheck and the following manual post-build step: dsymutil foo where foo is the name of the binary. See http://blog.mozilla.com/nnethercote/2009/02/17/valgrind-mac-os-x-update-feb-17-2009/ for more info about this spiffy branch of Valgrind. - Dan p.s. oh, yeah, I suppose I care about the error valgrind reported. Does libevent need to zero out some memory to avoid this? _______________________________________________ Libevent-users mailing list Libevent-users@monkey.org http://monkeymail.org/mailman/listinfo/libevent-users
