From: Tom Tromey <tromey@redhat.com>
To: Joachim Protze <joachim.protze@tu-dresden.de>
Cc: gdb@sourceware.org
Subject: Re: Pythons scripting API question
Date: Wed, 06 Jun 2012 17:58:00 -0000 [thread overview]
Message-ID: <877gvkiaqm.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4FCF7B43.8070700@tu-dresden.de> (Joachim Protze's message of "Wed, 06 Jun 2012 17:46:11 +0200")
>>>>> "Joachim" == Joachim Protze <joachim.protze@tu-dresden.de> writes:
Joachim> Thank you for this example!
Joachim> I never figured out this feature of Blocks :(
Keith> See the relevant sections in the Gdb Users Manual (23.2.2.16, 23.2.2.18).
Joachim> I totally miss the hint that Blocks drop Value objects on iteration in
Joachim> the documentation.
It was patched to be more clear:
2012-02-22 Tom Tromey <tromey@redhat.com>
* gdb.texinfo (Blocks In Python): Clarify block iteration.
The new text says:
A @code{gdb.Block} is iterable. The iterator returns the symbols
(@pxref{Symbols In Python}) local to the block. [...]
If this is insufficient, suggest more...
Joachim> How to access the "hierarchically organized" sub-blocks?
Unfortunately we are missing API for this.
Could you file a bug report for it?
Or alternatively, try to write it? I don't think gdb has a direct way
to iterate over sub-blocks; but at the very least you can iterate over
the blockvector and look for blocks with a certain parent.
Tom
prev parent reply other threads:[~2012-06-06 17:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-30 18:10 Evan Driscoll
2012-05-30 21:23 ` Keith Seitz
2012-05-30 22:42 ` Evan Driscoll
2012-05-30 23:12 ` Keith Seitz
2012-06-06 15:46 ` Joachim Protze
2012-06-06 17:58 ` Tom Tromey [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=877gvkiaqm.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb@sourceware.org \
--cc=joachim.protze@tu-dresden.de \
/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).