From: Cristian Zamfir <cristian.zamfir@epfl.ch>
To: Tom Tromey <tromey@redhat.com>
Cc: <gdb@sourceware.org>
Subject: Re: Python API iterate through the arguments of a frame
Date: Wed, 22 Feb 2012 15:41:00 -0000 [thread overview]
Message-ID: <13F5BBE8-C512-42C0-BA97-0BA1D2318CCC@epfl.ch> (raw)
In-Reply-To: <87wr7eq54e.fsf@fleche.redhat.com>
On Feb 22, 2012, at 4:06 PM, Tom Tromey wrote:
>>>>>> "Cristian" == Cristian Zamfir <cristian.zamfir@epfl.ch> writes:
>
> Cristian> Thank you, that would be very useful. Is there a quick way to see the
> Cristian> names of all available API functions, just in case there are more
> Cristian> undocumented ones, other than looking into the gdb/python/ directory
> Cristian> and infer from the Python bindings (e.g., py-block.c)?
>
> In addition to the other responses, I'd like to add that we want the
> documentation to be complete and clear; so please file bugs for any
> holes or problems you notice.
Sure, I will. Thanks everyone for the help.
>
> Cristian> I can however still retrieve the name and the value of the symbol when
> Cristian> loading a core. Is it possible to also get the type?
>
> Yes, this information is orthogonal to where the inferior memory comes
> from.
>
> Cristian> warning: core file may not match specified executable file.
> Cristian> warning: Can't read pathname for load map: Input/output error.
>
> These could be a problem, but offhand I can't say what is going on.
>
> I'm surprised about the AttributeError. I'm not sure how that could
> happen.
It turned out that when I was loading the core I used an older version of gdb (7.3), in which gdb.Symbol did not have the type attribute. Everything works with the latest version.
Thanks,
Cristi
>
> Tom
prev parent reply other threads:[~2012-02-22 15:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-21 15:55 Cristian Zamfir
2012-02-21 19:54 ` Tom Tromey
2012-02-21 22:52 ` Cristian Zamfir
2012-02-22 1:52 ` Paul_Koning
2012-02-22 8:54 ` Joachim Protze
2012-02-22 15:07 ` Tom Tromey
2012-02-22 15:41 ` Cristian Zamfir [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=13F5BBE8-C512-42C0-BA97-0BA1D2318CCC@epfl.ch \
--to=cristian.zamfir@epfl.ch \
--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