public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: "Martin Ünsal" <munsal@nestlabs.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Python API: Type introspection of function arguments
Date: Sun, 27 Sep 2015 23:28:00 -0000	[thread overview]
Message-ID: <CAFXXi0m_w1CftMZ5B6Q7Wta1mKDLPA_BAAxQZ7sxAZ8Vtkzoxw@mail.gmail.com> (raw)
In-Reply-To: <CAHHafQWq=XGR8JBJR8fSTJwWX2YUdcX0oS2kak_vbxT3xzA-dQ@mail.gmail.com>

On 25 September 2015 at 00:24, Martin Ünsal <munsal@nestlabs.com> wrote:
> Hi all,
>
> GDB Python bindings are great. I have a question though.
>
> I'm trying to use a Python script to introspect the type of a function
> argument. The GDB documentation claims this is possible:
> https://sourceware.org/gdb/current/onlinedocs/gdb/Types-In-Python.html#Types-In-Python
>
> "— Function: Type.fields ()
> For structure and union types, this method returns the fields. Range
> types have two fields, the minimum and maximum values. Enum types have
> one field per enum constant. Function and method types have one field
> per parameter."
>
> However when I try this (in 7.8.1.20141128-cvs) I get the following error:
>
>>>> sym = gdb.lookup_global_symbol('my_function')
>>>> print sym.type.code == gdb.TYPE_CODE_FUNC
> True
>>>> print sym.type.fields()
> Traceback (most recent call last):
>   File "<stdin>", line 1, in <module>
> TypeError: Type is not a structure, union, or enum type.
>>>>
>
> I also looked in the code (gdb/python/py-type.c) and this seems to
> have the same behavior in 7.10.
>
> In light of this issue, can anyone suggest how to get function
> argument type information from Python API?
>
> Thanks,
> Martin

Hi Martin,

I found a bug for that in the bugzilla:

  https://sourceware.org/bugzilla/show_bug.cgi?id=18073

I tested the feature with a few releases of gdb. It appeared it 7.1
and stopped working in 7.4, so it's been broken for quite a while.

The patch attached to the bug seems to make it work again. I am
running the regression testsuite at the moment. If it's successful,
I'll try to add a test for that and submit it... unless you want to do
it, of course :).

In the mean time, I don't have any suggestions to circumvent that,
other than building your own gdb (with the patch applied) for now.

Simon

  reply	other threads:[~2015-09-27 23:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-25  4:24 Martin Ünsal
2015-09-27 23:28 ` Simon Marchi [this message]
2015-09-28  4:50   ` Simon Marchi

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=CAFXXi0m_w1CftMZ5B6Q7Wta1mKDLPA_BAAxQZ7sxAZ8Vtkzoxw@mail.gmail.com \
    --to=simon.marchi@polymtl.ca \
    --cc=gdb@sourceware.org \
    --cc=munsal@nestlabs.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).