From: Tom Tromey <tromey@redhat.com>
To: Nathan Ridge <zeratul976@hotmail.com>
Cc: <gdb@sourceware.org>
Subject: Re: support for DWARF extensions used by GCC 4.7?
Date: Wed, 09 Nov 2011 14:21:00 -0000 [thread overview]
Message-ID: <m362itgyvy.fsf@fleche.redhat.com> (raw)
In-Reply-To: <BLU162-W7C897470EA71E2FB1DBC296DE0@phx.gbl> (Nathan Ridge's message of "Tue, 8 Nov 2011 20:13:02 +0000")
>>>>> "Nathan" == Nathan Ridge <zeratul976@hotmail.com> writes:
Nathan> "GCC now supports various new GNU extensions to the DWARF debugging
Nathan> information format, like entry value and call site information, typed
Nathan> DWARF stack or a more compact macro representation. Support for these
Nathan> extensions will come in GDB 7.4. They can be disabled through the
Nathan> -gstrict-dwarf command-line option."
Nathan> Has this support been added to GDB trunk?
Yes.
Nathan> I ask because I am trying to debug a program built with GCC trunk,
Nathan> with GDB trunk, and I am experiencing all sorts of weird behaviour
Nathan> (breakpoints being ignored, no line number given when a breakpoint
Nathan> is reached, inability to step into functions) that is usually
Nathan> indicative of the generated debug info format and the format expected
Nathan> by the debugger not being in sync.
Nathan> On the other hand, adding -gstrict-dwarf when compiling does not
Nathan> help, so it may be a different issue...
Yeah, probably so. If you have reasonably easy ways to reproduce the
bugs, we're interested -- file in bugzilla.
Tom
prev parent reply other threads:[~2011-11-09 14:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-08 20:13 Nathan Ridge
2011-11-09 14:21 ` Tom Tromey [this message]
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=m362itgyvy.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb@sourceware.org \
--cc=zeratul976@hotmail.com \
/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).