Author Topic: Problems with gdb  (Read 2957 times)

uhu01

  • Guest
Problems with gdb
« on: December 03, 2005, 10:39:47 pm »
Hy!

I use C::B v1.0rc2 on WinXPSP2. I'm using the gdb that is packed to C::B.
My Problem is the following: I know that there is a bug in C::B in this version with gdb.
So I tried to debug as it was mentioned in a thread below. I tried to use "run to cursor" to stop debugger at a specified line, but it didn't worked. Then I tried to debug using "Step into", then setting the breakpoint, and execute the program to the breakpoint using "Debug/Continue" or "Run to cursor" in this state (programm stopped in main).

I thought it may depend on gdb, and tried to debug from command line, this worked perfectly. The only things that were a little disturbing were the lines
Code: [Select]
(gdb) run
ContinueDebugEvent (cpid=1660, ctid=1668, DBG_CONTINUE);
ContinueDebugEvent (cpid=1660, ctid=1668, DBG_CONTINUE);
gdb: child_close, inferior_ptid=1668
Starting program: C:\Dokumente und Einstellungen\Administrator\Eigene Dateien\programming\test/test.exe
gdb: do_initial_child_stuff: process 1800
gdb: kernel event for pid=1800 tid=1584 code=CREATE_PROCESS_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 1800.0x630
ContinueDebugEvent (cpid=1800, ctid=1584, DBG_CONTINUE);
gdb: kernel event for pid=1800 tid=1584 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 1800.0x630
ContinueDebugEvent (cpid=1800, ctid=1584, DBG_CONTINUE);
gdb: kernel event for pid=1800 tid=1584 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 1800.0x630
ContinueDebugEvent (cpid=1800, ctid=1584, DBG_CONTINUE);
gdb: kernel event for pid=1800 tid=1584 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 1800.0x630
ContinueDebugEvent (cpid=1800, ctid=1584, DBG_CONTINUE);
gdb: kernel event for pid=1800 tid=1584 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 1800.0x630
ContinueDebugEvent (cpid=1800, ctid=1584, DBG_CONTINUE);
gdb: kernel event for pid=1800 tid=1584 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 1800.0x630
ContinueDebugEvent (cpid=1800, ctid=1584, DBG_CONTINUE);
...
...
gdb: kernel event for pid=1800 tid=1584 code=LOAD_DLL_DEBUG_EVENT)
gdb: child_resume.SetThreadContext: thread 1800.0x630
ContinueDebugEvent (cpid=1800, ctid=1584, DBG_CONTINUE);
gdb: kernel event for pid=1800 tid=1584 code=EXIT_PROCESS_DEBUG_EVENT)

Program exited normally.
ContinueDebugEvent (cpid=1800, ctid=1584, DBG_CONTINUE);
gdb: child_close, inferior_ptid=1584
There were about 200 of this lines, all exactly the same.

Another problem is that C::B freezes for about 10 second every time i execute gdb from C::B using "step into", after it isn't freezed any more I hit "step into" a second time to step into main(...) function. Then C::B jumps into a self written header. It's every time the same, C::B highlights the same line as every time before, and I can't finish debugging with another button than "debug/continue" but this executes the programm tilll the end.

Is there any workaround for this?

regards
uhu01