From: <Paul_Koning@Dell.com>
To: <sivachandra@google.com>, <dje@google.com>
Cc: <gdb-patches@sourceware.org>
Subject: RE: [RFC - Python Scripting] New method Objfile.symtabs () - docs included
Date: Thu, 05 Apr 2012 16:30:00 -0000 [thread overview]
Message-ID: <09787EF419216C41A903FD14EE5506DD0313D5BF45@AUSX7MCPC103.AMER.DELL.COM> (raw)
In-Reply-To: <CAGyQ6gwwnySK=2hxRj9fWDsxKt0Vqan7O_Lb3hrQt7gX7Me1SA@mail.gmail.com>
> Assuming we want to provide the ability to iterate over all the symbol
> tables, we want to be able to do that without first expanding them.
> So I think the first question is what will the user want to do with
> this feature?
Something else I'm looking for, and this seems to be a step in that direction, is a way to iterate over all the defined types. For example, I want to do some checking similar to what "pahole" does. The command line utility by that name processes all the types but its output is hard to handle. The Python machinery to do the equivalent on a single type is already in place, but how do I get all the types defined in my program? Those presumably live in a symtab but I didn't see a gdb.Symtab method to get them. (Is that the right approach? I can work on creating the machinery if this is the place for them, or if someone can point me to where in the gdb.* class hierarchy to fit this.)
paul
next prev parent reply other threads:[~2012-04-05 16:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-02 6:17 Siva Chandra
2012-04-02 17:08 ` Eli Zaretskii
2012-04-03 0:04 ` Doug Evans
2012-04-03 5:54 ` Siva Chandra
2012-04-05 16:30 ` Paul_Koning [this message]
2012-04-05 18:41 ` Tom Tromey
2012-04-05 18:37 ` Tom Tromey
2012-04-05 19:56 ` Paul_Koning
2012-04-05 20:26 ` Doug Evans
2012-04-06 16:42 ` Siva Chandra
2012-04-09 17:56 ` Tom Tromey
2012-04-09 17:59 ` Doug Evans
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=09787EF419216C41A903FD14EE5506DD0313D5BF45@AUSX7MCPC103.AMER.DELL.COM \
--to=paul_koning@dell.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=sivachandra@google.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