Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Phil Muldoon <pmuldoon@redhat.com>
To: Marcelo Taube <mail.marcelo.taube@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Some feedback about the python scripting feature
Date: Tue, 10 Nov 2009 15:12:00 -0000	[thread overview]
Message-ID: <4AF93ECD.60807@redhat.com> (raw)
In-Reply-To: <4AF8993D.2050507@gmail.com>

On 11/09/2009 10:35 PM, Marcelo Taube wrote:
> Dear gdb team,
>
> I have been using the python scripting feature of gdb7
>
> The feature is great it let me debug my code much better and in a much 
> flexible way.
>
> There are some features missing which would improve it even more, though.
>
> I want to mention them in case noone did it before.


Thanks.  I'll comment on the two things I know about:


>
>    * *calling functions*: From regular gdb command line the user can
>      allways simply do " p foo()" to call function and print the
>      result, it would be usefull to be able to call C functions (or the
>      debugged lenguage) from python and get the result as a Value
>      object in the same way a variable is accessed.

There is a patch in the works:

http://sourceware.org/ml/archer/2009-q3/msg00206.html

But for right now you can use:

  foo = gdb.parse_and_eval("foo(bar)")


>    * *equality of types: *i think there are problems with the equality
>      of types in gdb. Look at the case that  two type objects were
>      obtained and represent the same type, the expression
>      'gdb.lookup_type("int") == gdb.lookup_type("int")' now returns
>      false but it should return true.

There was an enhancement filed for this:


http://sourceware.org/bugzilla/show_bug.cgi?id=10676


Regards

Phil


  reply	other threads:[~2009-11-10 10:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4AF898F3.50908@gmail.com>
2009-11-10  8:06 ` Marcelo Taube
2009-11-10 15:12   ` Phil Muldoon [this message]
2009-11-10 15:38   ` Tom Tromey
2009-11-10 16:53     ` Daniel Jacobowitz
2009-11-10 20:49       ` Marcelo Taube
2009-11-11  2:00         ` Daniel Jacobowitz
2009-11-13 21:37       ` scott snyder

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=4AF93ECD.60807@redhat.com \
    --to=pmuldoon@redhat.com \
    --cc=gdb@sourceware.org \
    --cc=mail.marcelo.taube@gmail.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