* Problems with debugging programs with multiple binaries
@ 2008-02-10 16:01 Fabian Lenzen
0 siblings, 0 replies; only message in thread
From: Fabian Lenzen @ 2008-02-10 16:01 UTC (permalink / raw)
To: gdb
Hi,
I am using the MinGW Version of GDB 6.6, so I do not know whether this is a general GDB problem, or it does only occur with the Windows version.
The problem I have occurs while debugging executables and dynamic libraries (DLLs). The executable is only written to get a starting point to debug the DLL. Both are compiled with the MinGW Gnu compiler, with debugging symbols (-g3) and without optimization (-O0).
I can start the debugging session correctly, and step through all functions that are defined in the executable. Now, I try to step into a function that is located in the DLL. Instead of the source file, I am taken to iostream, line 77 (which contains âstatic ios_base::Init __ioinit;â). I can âstepâ again to reach the code line I want to, but having always this file is annoying, but â much worse â makes my IDE(Eclipse/CDT) hang up in a endless loop, so I cannot use my IDE there.
I already posted in the CDT newsgroup, but isn't is possible to make GDB directly step into the source file I want to see? And, what does this code line have to do with the function call?
Maybe someone can help me,
Fabian
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2008-02-10 16:01 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-02-10 16:01 Problems with debugging programs with multiple binaries Fabian Lenzen
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox