Thanks for reply.
And keep in mind that the idbg should produce the same output to the commands as gdb,
if the output format is different a new debugger plugin should be written to implement correct communication with idbg.
I understand this.
Also we have a branch, where we have done many improvements to the debugging in C::B, you can check it out, it is named wxpropgrid_debugger.
I will test this branch.
As I said, I can't understand, why "cb_gdb:" prompt is not caught. I think that problem is with wxProcess not with C::B. Could it be?
Below is debug log of the debugger. Because "cb_gdb:" prompt is not caught, C::B never comes to the second command in the queue. If I debug a test program using command line in the terminal, the output of gdb and idbc debuggers looks the same.
LD_LIBRARY_PATH=.:"/bin/ia32:/debugger/lib/ia32:/debugger/gui/ia32"
Command-line: /opt/intel/composerxe-2011.2.137/bin/ia32/idbc -gdb -nx -fullname -quiet -args bin/Debug/gdb_test
Working dir : /home/darius/Programavimas/idb_test/
> set prompt >>>>>>cb_gdb:
Executing: xterm -T 'Program Console' -e sleep 84792
Executing: ps x -o tty,pid,command
Reading symbols from /home/darius/Programavimas/idb_test/bin/Debug/idb_test...done.
PS result: pts/1 5000 ps x -o tty,pid,command
PS result: pts/1 4999 bin/Debug/idb_test
PS result: pts/6 4997 sleep 84792
TTY is[/dev/pts/6]
GetConsoleTTY[/dev/pts/6]ConsolePid[4995]
Queued:[tty /dev/pts/6]