From: Tom Tromey <tromey@redhat.com>
To: Vimal <j.vimal@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Collecting description of types from symbol table
Date: Mon, 05 Mar 2012 16:36:00 -0000 [thread overview]
Message-ID: <87y5rfvwcj.fsf@fleche.redhat.com> (raw)
In-Reply-To: <CAK3Ji10Z_6CiaH_CDtEGSYG6UUugm0B85Mdb8txbcSn74dji8g@mail.gmail.com> (Vimal's message of "Thu, 1 Mar 2012 18:56:57 -0800")
>>>>> "Vimal" == Vimal <j.vimal@gmail.com> writes:
Vimal> I would like to dump the collect the output of the "ptype" command for
Vimal> all possible types that gdb is aware of.
Vimal> For example, the following output is very useful when debugging the
Vimal> kernel, and I would like to collect the output of all such types in
Vimal> the kernel for reference. Could someone tell me rough ideas of how
Vimal> this is stored in the executable, and how to dump this?
Usually it is stored in DWARF format.
See http://dwarfstd.org/
Iterating over all the types, in gdb, is not trivial.
It could be done but you will have to write some C code to do it.
The 7 dwarves project would be an ok place to start for this though.
pahole nearly does it already.
Tom
next prev parent reply other threads:[~2012-03-05 16:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-02 2:57 Vimal
2012-03-05 16:36 ` Tom Tromey [this message]
2012-03-06 23:16 ` Vimal
2012-03-07 3:15 ` Tom Tromey
2012-03-08 16:51 ` Vimal
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=87y5rfvwcj.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb@sourceware.org \
--cc=j.vimal@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).