From: Daniel Jacobowitz <drow@false.org>
To: Paul Koning <pkoning@equallogic.com>
Cc: gdb@sources.redhat.com
Subject: Re: preprocessor support?
Date: Fri, 28 May 2004 19:29:00 -0000 [thread overview]
Message-ID: <20040528192945.GA4018@nevyn.them.org> (raw)
In-Reply-To: <16567.37347.995508.204649@gargle.gargle.HOWL>
On Fri, May 28, 2004 at 03:24:19PM -0400, Paul Koning wrote:
> These days GCC will output dwarf2 debug sections listing preprocessor
> symbol definitions, but gdb 6.1 doesn't seem to look at that (at least
> not for mips-netbsd).
>
> Is that not implemented yet? Is it in some targets but not this one
> (and if so, any pointers to places I might look to teach this target a
> new trick)?
It should work everywhere, so you'll have to dig at it harder. I'm not
sure that it's tested; there's at least one test in the testsuite but I
don't see it going out of its way to pass -g3, so the binary won't have
macro information.
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-05-28 19:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-28 19:24 Paul Koning
2004-05-28 19:29 ` Daniel Jacobowitz [this message]
2004-05-28 19:35 ` Paul Koning
2004-06-01 1:43 ` Daniel Jacobowitz
2004-06-01 14:49 ` Paul Koning
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=20040528192945.GA4018@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=pkoning@equallogic.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