Bug#585809: valgrind: stripped ld.so causes tons of false positives
On Sun, Jun 13, 2010 at 04:48:09PM -0700, Nick Lewycky wrote:
> Package: valgrind
> Version: 1:3.5.0-3
> Severity: important
>
> A change in /lib/ld-linux.so.2 has made valgrind report an excess number of
> errors:
>
> $ valgrind /bin/true
> ==6032== Memcheck, a memory error detector
> ==6032== Copyright (C) 2002-2009, and GNU GPL'd, by Julian Seward et al.
> ==6032== Using Valgrind-3.5.0-Debian and LibVEX; rerun with -h for copyright info
> ==6032== Command: /bin/true
> ==6032==
> ==6032== Conditional jump or move depends on uninitialised value(s)
> ==6032== at 0x4416471: strlen (strlen.S:110)
> ==6032== by 0x4407C04: _dl_init_paths (dl-load.c:776)
> ==6032== by 0x4402A2C: dl_main (rtld.c:1393)
> ==6032== by 0x44141D6: _dl_sysdep_start (dl-sysdep.c:243)
> ==6032== by 0x4400C6C: _dl_start (rtld.c:338)
> ==6032== by 0x4400856: ??? (in /lib/ld-2.11.1.so)
> [... snip 12 more error reports ...]
> ==6032== HEAP SUMMARY:
> ==6032== in use at exit: 0 bytes in 0 blocks
> ==6032== total heap usage: 0 allocs, 0 frees, 0 bytes allocated
> ==6032==
> ==6032== All heap blocks were freed -- no leaks are possible
> ==6032==
> ==6032== For counts of detected and suppressed errors, rerun with: -v
> ==6032== Use --track-origins=yes to see where uninitialised values come from
> ==6032== ERROR SUMMARY: 13 errors from 8 contexts (suppressed: 0 from 0)
>
> The problem is doucmented upstream as the first note in the notes for packagers:
>
> http://valgrind.org/docs/manual/dist.readme-packagers.html
>
> Please fix this, presumably by negotiating with the libc6 folks or maybe just
> reassigning it to them. Thanks!
>
The recommendations are already followed, libc6-dbg provides the
debugging symbols of ld.so and valgrind depends on it.
There is nothing we can do on the eglibc side.
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
Reply to: