|
From: <wim...@ad...> - 2009-02-09 15:52:16
|
I asked this question before, but I think I have some more info. first a resume. When Valgrind (valgrind-3.3.0-Debian) stops and ask to start the debugger, when you say 'y' the gdb debugger starts. However gdb claims that the program it is requested to debug is already being debugged. So I wonder if the PID that is passed to gdb is the correct process. So, when valgrind says ==2000== starting debugger with cmd: /usr/bin/gdb -nw /proc/2006/fd/1014 2006 GNU gdb 6.8-debian Copyright (C) 2008 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"... Attaching to program: /proc/2006/fd/1014, process 2006 Cannot access memory at address 0x448a0003 A program is being debugged already. Kill it? (y or n) the ps -axf shows 2000 /usr/bin/valgrind.bin --db-attach=yes --num-callers=20 AP 2006 \_ /usr/bin/valgrind.bin --db-attach=yes --num-callers=2 2007 \_ /bin/sh -c /usr/bin/gdb -nw /proc/2006/fd/1014 2006 2008 \_ /usr/bin/gdb -nw /proc/2006/fd/1014 2006 |