From: "Fabian Lenzen" <fabian.lenzen@web.de>
To: gdb@sourceware.org
Subject: Problems with debugging programs with multiple binaries
Date: Sun, 10 Feb 2008 16:01:00 -0000 [thread overview]
Message-ID: <op.t6bf16r4sbabl2@medion.speedport_w_700v> (raw)
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
reply other threads:[~2008-02-10 16:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=op.t6bf16r4sbabl2@medion.speedport_w_700v \
--to=fabian.lenzen@web.de \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox