From: Joachim Protze <joachim.protze@tu-dresden.de>
To: gdb@sourceware.org
Subject: Re: Pythons scripting API question
Date: Wed, 06 Jun 2012 15:46:00 -0000 [thread overview]
Message-ID: <4FCF7B43.8070700@tu-dresden.de> (raw)
In-Reply-To: <4FC68FD0.4060809@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1152 bytes --]
On 30.05.2012 23:23, Keith Seitz wrote:
> Frames contain blocks, blocks contain variables. Blocks in python can
> be iterated, so:
>
> $ ./gdb -nx -q gdb -ex "break main" -ex "run"
> (gdb) python import gdb
> (gdb) python for n in gdb.selected_frame().block(): print n,
> argc argv args
> (gdb) python print n.type
> struct captured_main_args
> (gdb) python print n.name
> args
> (gdb) python print n.is_argument
> False
> (gdb) python print n.value(gdb.selected_frame())
> {argc = 0, argv = 0x488f80 <_start>, use_windows = -8032,
> interpreter_p = 0x0}
>
Thank you for this example!
I never figured out this feature of Blocks :(
> See the relevant sections in the Gdb Users Manual (23.2.2.16, 23.2.2.18).
I totally miss the hint that Blocks drop Value objects on iteration in
the documentation.
How to access the "hierarchically organized" sub-blocks? Or did I
missunderstand the concept of Blocks?
main()
{
int i;
for(...)
{
int a;
}
{
int i;
}
}
I would expect a Block for the main function with two children Blocks -
but how to get these children?
- Joachim
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5306 bytes --]
next prev parent reply other threads:[~2012-06-06 15:46 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 [this message]
2012-06-06 17:58 ` Tom Tromey
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=4FCF7B43.8070700@tu-dresden.de \
--to=joachim.protze@tu-dresden.de \
--cc=gdb@sourceware.org \
/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