On Thu, Mar 25, 2010 at 11:09:36AM -0300, Crístian Viana wrote: > hi, > > when I use valgrind, it shows hundreds of warnings related to glibc. here's > one example, from "valgrind ls": > > ==10023== Use of uninitialised value of size 8 > ==10023== at 0x55605A4: (within /lib64/libc-2.10.1.so) > ==10023== by 0x5560111: (within /lib64/libc-2.10.1.so) > ==10023== by 0x4A1E62C: _vgnU_freeres (in > /usr/lib64/valgrind/amd64-linux/vgpreload_core.so) > ==10023== by 0x548CE84: (within /lib64/libc-2.10.1.so) > ==10023== by 0x548CEF4: exit (in /lib64/libc-2.10.1.so) > ==10023== by 0x40864D: (within /bin/ls) > ==10023== by 0x5476A25: (below main) (in /lib64/libc-2.10.1.so) > > while that happens, I can't use valgrind because there's too much noise > besides my program's [possible] memory errors. > > any idea of why is this happening? I reemerged =sys-libs/glibc-2.10.1-r1 but > nothing has changed. > > cheers, > Crístian. You may want to look into supressions. There's an option called --gen-suppressions. See the man page for details.
-- I am a man who does not exist for others.
pgp5VUL5Q1HwM.pgp
Description: PGP signature
