Package: valgrind Version: 1:3.5.0-2 Severity: important Hi.
I recently updated my libc6 and after the update (which probably removed my libc6-dbg due to some other problem), valgrind threw huge amounts of false positives. I asked at the valgrind-users mailinglist and the problem is with valgrind not knowing the right glibc version or assuming a wrong one. I don't know the details, but valgrind has to know the version of it to be able to warn the user about missing debug symbols. This is not the case, if the debug symbols are there. And those are in the libc6-dbg package. Valgrind (memcheck at least) needs the debug symbols from libc6 to function properly. If valgrind knows the libc version it can tell the user to install them, but if not, it breaks. Setting the libc6-dbg package as a dependency will resolve this problem. It needs them anyway. For the original thread on the valgrind-users list see: http://sourceforge.net/mailarchive/forum.php?thread_name=4B010952.8000709%40googlemail.com&forum_name=valgrind-users Greetings Andre -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.30-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages valgrind depends on: ii libc6 2.10.1-7 GNU C Library: Shared libraries Versions of packages valgrind recommends: ii gdb 6.8.50.20090628-4 The GNU Debugger Versions of packages valgrind suggests: pn alleyoop <none> (no description available) ii kcachegrind 4:4.3.2-1 visualisation tool for the Valgrin ii libc6-dbg 2.10.1-7 GNU C Library: detached debugging -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
