hi,<div><br></div><div>when I use valgrind, it shows hundreds of warnings related to glibc. here&#39;s one example, from &quot;valgrind ls&quot;:</div><div><br></div><div><div>==10023== Use of uninitialised value of size 8</div>

<div>==10023==    at 0x55605A4: (within /lib64/<a href="http://libc-2.10.1.so">libc-2.10.1.so</a>)</div><div>==10023==    by 0x5560111: (within /lib64/<a href="http://libc-2.10.1.so">libc-2.10.1.so</a>)</div><div>==10023==    by 0x4A1E62C: _vgnU_freeres (in /usr/lib64/valgrind/amd64-linux/vgpreload_core.so)</div>

<div>==10023==    by 0x548CE84: (within /lib64/<a href="http://libc-2.10.1.so">libc-2.10.1.so</a>)</div><div>==10023==    by 0x548CEF4: exit (in /lib64/<a href="http://libc-2.10.1.so">libc-2.10.1.so</a>)</div><div>==10023==    by 0x40864D: (within /bin/ls)</div>

<div>==10023==    by 0x5476A25: (below main) (in /lib64/<a href="http://libc-2.10.1.so">libc-2.10.1.so</a>)</div><div><br></div><div>while that happens, I can&#39;t use valgrind because there&#39;s too much noise besides my program&#39;s [possible] memory errors.</div>

<div><br></div><div>any idea of why is this happening? I reemerged =sys-libs/glibc-2.10.1-r1 but nothing has changed.</div><div><br></div><div>cheers,</div><div>Crístian.</div></div>