Package: valgrind Version: 1:3.7.0-6 Severity: normal When running
valgrind --log-file=valgrind.log --vgdb=full --vgdb-error=1 rtorrent I found ==27729== TO DEBUG THIS PROCESS USING GDB: start GDB like this ==27729== /path/to/gdb rtorrent ==27729== and then give GDB the following command ==27729== target remote | /usr/lib/valgrind/../../bin/vgdb --pid=27729 ==27729== --pid is optional if only one valgrind process is running in the valgrind.log. However, doing so resulted in % gdb rtorrent GNU gdb (GDB) 7.4.1-debian Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i486-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/bin/rtorrent...(no debugging symbols found)...done. (gdb) target remote | /usr/lib/valgrind/../../bin/vgdb --pid=27729 Remote debugging using | /usr/lib/valgrind/../../bin/vgdb --pid=27729 vgdb error: no FIFO found matching pid 27729 Remote communication error. Target disconnected.: Ресурс временно недоступен. Luckily I remebered that valgrind created some files in /tmp/ instead of $TMPDIR. So I was able to connect to valgrind using % env --unset=TMPDIR gdb rtorrent -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (900, 'testing'), (400, 'stable') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages valgrind depends on: ii libc6 2.13-33 ii libc6-dbg 2.13-33 Versions of packages valgrind recommends: ii gdb 7.4.1-1.1 ii valgrind-dbg 1:3.7.0-6 Versions of packages valgrind suggests: pn alleyoop <none> pn kcachegrind <none> pn valgrind-mpi <none> pn valkyrie <none> -- 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
