From: Vimal <j.vimal@gmail.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb@sourceware.org
Subject: Re: Collecting description of types from symbol table
Date: Tue, 06 Mar 2012 23:16:00 -0000 [thread overview]
Message-ID: <CAK3Ji1017TYOxxk43dPwmoyrPqm6Q7Re7AWxcOHKUuCSbcZTYw@mail.gmail.com> (raw)
In-Reply-To: <87y5rfvwcj.fsf@fleche.redhat.com>
Hi Tom,
On 5 March 2012 08:36, Tom Tromey <tromey@redhat.com> wrote:
>
> 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.
DWARF standard pointed me to dwarfdump, which seems to dump the type
information stored in an object file.
> The 7 dwarves project would be an ok place to start for this though.
> pahole nearly does it already.
pahole is interesting, but it looks like its repository on kernel.org
is down. I'll contact the author.
Thanks!
--
Vimal
next prev parent reply other threads:[~2012-03-06 23:16 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
2012-03-06 23:16 ` Vimal [this message]
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=CAK3Ji1017TYOxxk43dPwmoyrPqm6Q7Re7AWxcOHKUuCSbcZTYw@mail.gmail.com \
--to=j.vimal@gmail.com \
--cc=gdb@sourceware.org \
--cc=tromey@redhat.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