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