Package: valgrind Version: 1:3.6.1-4 Severity: important Tags: sid When trying to attach to the debugger, I get output like:
==30890== ---- Attach to debugger ? --- [Return/N/n/Y/y/C/c] ---- y ==30890== starting debugger with cmd: /home/madcoder/bin/gdb -nw /proc/30900/fd/1014 30900 /bin/sh: /home/madcoder/bin/gdb: not found and indeed, running strings on files in /usr/lib/valgrind shows that they have /home/madcoder/bin/gdb hard-coded. Rebuilding the package via 'dpkg-buildpackage' fixes it for me, so presumably it was some custom environment cruft which slipped into the package build of 3.6.1-4. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages valgrind depends on: ii libc6 2.13-4 Embedded GNU C Library: Shared lib pn libc6-dbg <none> (no description available) Versions of packages valgrind recommends: ii gdb 7.2-1 The GNU Debugger Versions of packages valgrind suggests: pn alleyoop <none> (no description available) pn kcachegrind <none> (no description available) pn valkyrie <none> (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
