From: Ian Lance Taylor <iant@google.com>
To: Michael Bauer <mvbauer@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Question regarding exporting data type information during compilation
Date: Tue, 23 Feb 2010 18:24:00 -0000 [thread overview]
Message-ID: <mcrfx4rddc3.fsf@dhcp-172-17-9-151.mtv.corp.google.com> (raw)
In-Reply-To: <AF2460ED-BEA5-4F7F-AC45-77A7119B5D0E@gmail.com> (Michael Bauer's message of "Thu\, 18 Feb 2010 21\:30\:35 -0800")
Michael Bauer <mvbauer@gmail.com> writes:
> Another thought that I had, if the compiler is not capable of
> outputting this information, then perhaps there is some debug
> information file that I could write a script to parse. I'm thinking
> that debuggers somehow know the symbol name, address, and type so it
> must be output into some sort of debugging file. If anyone has any
> suggestions I would be much appreciative.
You can use readelf --debug-dump to dump all sorts of information
about the debugging information.
The compiler won't dump it for you, unless you count looking at the
assembler output when using -S -dA.
Ian
prev parent reply other threads:[~2010-02-23 18:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-19 6:34 Michael Bauer
2010-02-23 18:24 ` Ian Lance Taylor [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=mcrfx4rddc3.fsf@dhcp-172-17-9-151.mtv.corp.google.com \
--to=iant@google.com \
--cc=gcc-help@gcc.gnu.org \
--cc=mvbauer@gmail.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).