| 1 |
hi, |
| 2 |
|
| 3 |
when I use valgrind, it shows hundreds of warnings related to glibc. here's |
| 4 |
one example, from "valgrind ls": |
| 5 |
|
| 6 |
==10023== Use of uninitialised value of size 8 |
| 7 |
==10023== at 0x55605A4: (within /lib64/libc-2.10.1.so) |
| 8 |
==10023== by 0x5560111: (within /lib64/libc-2.10.1.so) |
| 9 |
==10023== by 0x4A1E62C: _vgnU_freeres (in |
| 10 |
/usr/lib64/valgrind/amd64-linux/vgpreload_core.so) |
| 11 |
==10023== by 0x548CE84: (within /lib64/libc-2.10.1.so) |
| 12 |
==10023== by 0x548CEF4: exit (in /lib64/libc-2.10.1.so) |
| 13 |
==10023== by 0x40864D: (within /bin/ls) |
| 14 |
==10023== by 0x5476A25: (below main) (in /lib64/libc-2.10.1.so) |
| 15 |
|
| 16 |
while that happens, I can't use valgrind because there's too much noise |
| 17 |
besides my program's [possible] memory errors. |
| 18 |
|
| 19 |
any idea of why is this happening? I reemerged =sys-libs/glibc-2.10.1-r1 but |
| 20 |
nothing has changed. |
| 21 |
|
| 22 |
cheers, |
| 23 |
Crístian. |
Archives