Bug #12470 2007-11-18 16:58
tpetrov
Unable to stop the debug process! message box
When I try to debug any project I get a message box: "Unable to stop the debug process!" and I have to kill gdb and the debugged app to stop it.
If I set a break point before hitting F8 it stops on it, but if I hit F8 it can't be stopped from Code::Blocks.
After little investigation of the problem I found that:
void DebuggerDriver::SetChildPID(long pid) is never called on linux (don't know about windows, there it might work).
And here is the debug log of the debugger:
LD_LIBRARY_PATH=.:~/projects/codeblocks/trunk/src/devel
Command-line: /usr/bin/gdb -nx -fullname -quiet -args ./cmd_purple
Working dir : /home/obfuscated/projects/cmd_purple/
> set prompt >>>>>>cb_gdb:
Executing: xterm -e sleep 110143
[?1034hUsing host libthread_db library "/lib/libthread_db.so.1".
(gdb) >>>>>>cb_gdb:
> show version
GNU gdb 6.6
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
>>>>>>cb_gdb:
> set confirm off
>>>>>>cb_gdb:
> set width 0
>>>>>>cb_gdb:
> set height 0
>>>>>>cb_gdb:
> set breakpoint pending on
>>>>>>cb_gdb:
> set print asm-demangle on
>>>>>>cb_gdb:
> set unwindonsignal on
>>>>>>cb_gdb:
> set disassembly-flavor intel
>>>>>>cb_gdb:
> directory /home/obfuscated/projects/cmd_purple/
>>>>>>cb_gdb:
Executing: ps x -o tty,pid,command
PS result: pts/2 30197 ps x -o tty,pid,command
PS result: pts/3 30195 sleep 110143
TTY is[/dev/pts/3]
GetConsoleTTY[/dev/pts/3]ConsolePid[30193]
> tty /dev/pts/3
Queued:[tty /dev/pts/3]
>>>>>>cb_gdb:
> run
[Thread debugging using libthread_db enabled]
[New Thread 47851103670336 (LWP 30198)]
- Category
- Debugger
- Group
- Status
- Closed
- Close date
- 2008-01-10 11:27
- Assigned to
History
OS is gentoo linux 64bit, wxWidgets 2.8.6, gcc 4.1.2 c::b rev 4640
This bug is now fixed in HEAD.
Thank you for reporting it.