* [gentoo-user] valgrind showing glibc warnings
@ 2010-03-25 14:09 99% Crístian Viana
0 siblings, 0 replies; 1+ results
From: Crístian Viana @ 2010-03-25 14:09 UTC (permalink / raw
To: gentoo-user
[-- Attachment #1: Type: text/plain, Size: 863 bytes --]
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.
[-- Attachment #2: Type: text/html, Size: 1289 bytes --]
^ permalink raw reply [relevance 99%]
Results 1-1 of 1 | reverse | options above
-- pct% links below jump to the message on this page, permalinks otherwise --
2010-03-25 14:09 99% [gentoo-user] valgrind showing glibc warnings Crístian Viana
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox