From: Chris S. <ir0...@gm...> - 2009-10-11 14:06:20
|
> Hello, I'm sorry, I don't know how to manually build the GDB.exe from > the source, is there any step instructions? It may not be necessary... > A: > The console DebugBreak program works(TDM-MinGW 4.4.1 + GDB.exe 7.0)!!! > > which means when I start debugging from the command line. (debuggee.exe > was build from TDM) such as: > > gdb.exe debuggee.exe > > then I manually run: DebugBreak.exe pid_of_debuggee > > then gdb.exe will report something like below, and return to the command > prompt: > > Program received signal SIGTRAP, Trace/breakpoint trap. > [Switching to Thread 2188.0x9f8] > 0x7c90120f in ?? () > (gdb)_ This is expected, you have managed to pause the process. You should be able to set breakpoints and execute backtraces, etc. from this prompt. > ---------------------------------------------------------------------------- > > B: I found that the GDB.exe 7.0 *can't* set breakpoints on an DLL's > source file. > > For example I have A.cpp->A.exe and B.cpp->B.dll. > > Then A.exe depend on the B.dll. > > When I debug A.exe, I *can* set breakpoints in A.cpp, but I *can't* set > breakpoints in B.cpp. > > In GDB.exe 6.8.3, breakpoints can set in both A.cpp and B.cpp. > > I have added the test code in C::B forum post: > http://forums.codeblocks.org/index.php/topic,11301.msg77123.html#msg77123 I'll take a look at this in a couple of days, since I'm swamped with other stuff at the moment. I'll let you know how I make out... Cheers! Chris -- Chris Sutcliffe http://emergedesktop.org |