From: Nathan Ridge <zeratul976@hotmail.com>
To: <gdb@sourceware.org>
Subject: support for DWARF extensions used by GCC 4.7?
Date: Tue, 08 Nov 2011 20:13:00 -0000 [thread overview]
Message-ID: <BLU162-W7C897470EA71E2FB1DBC296DE0@phx.gbl> (raw)
Hi,
The following in stated on the GCC website [1]:
"GCC now supports various new GNU extensions to the DWARF debugging
information format, like entry value and call site information, typed
DWARF stack or a more compact macro representation. Support for these
extensions will come in GDB 7.4. They can be disabled through the
-gstrict-dwarf command-line option."
Has this support been added to GDB trunk?
I ask because I am trying to debug a program built with GCC trunk,
with GDB trunk, and I am experiencing all sorts of weird behaviour
(breakpoints being ignored, no line number given when a breakpoint
is reached, inability to step into functions) that is usually
indicative of the generated debug info format and the format expected
by the debugger not being in sync.
On the other hand, adding -gstrict-dwarf when compiling does not
help, so it may be a different issue...
Thanks,
Nate
[1] http://gcc.gnu.org/gcc-4.7/changes.html
next reply other threads:[~2011-11-08 20:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-08 20:13 Nathan Ridge [this message]
2011-11-09 14:21 ` Tom Tromey
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=BLU162-W7C897470EA71E2FB1DBC296DE0@phx.gbl \
--to=zeratul976@hotmail.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).