From: Phil Muldoon <pmuldoon@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org, Eli Zaretskii <eliz@gnu.org>
Subject: Re: [patch] Allow gdb.Values to become callable if appropriate.
Date: Wed, 28 Jul 2010 09:47:00 -0000 [thread overview]
Message-ID: <4C4FFCAB.4040909@redhat.com> (raw)
In-Reply-To: <m3mxtcpyu0.fsf@fleche.redhat.com>
On 27/07/10 19:24, Tom Tromey wrote:
> Phil> So committed
> Phil> http://sourceware.org/ml/gdb-cvs/2010-07/msg00156.html
>
> Could you please make a NEWS patch that mentions the new Python
> improvements on the trunk? Thanks.
Here is a patch. What do you think?
Cheers,
Phil
ChangeLog
2010-07-28 Phil Muldoon <pmuldoon@redhat.com>
* NEWS: Document Python value inferior function calls.
--
diff --git a/gdb/NEWS b/gdb/NEWS
index 0aea3fb..73f79a5 100644
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -3,6 +3,15 @@
*** Changes since GDB 7.2
+* Python scripting
+
+ ** GDB values in Python are now callable if the value represents a
+ function. For example, if 'some_value' represents a function that
+ takes two integer parameters and returns a value, you can call
+ that function like so:
+
+ result = some_value (10,20)
+
* GDB now has some support for using labels in the program's source in
linespecs. For instance, you can use "advance label" to continue
execution to a label.
next prev parent reply other threads:[~2010-07-28 9:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-19 10:40 Phil Muldoon
2010-07-20 22:17 ` Tom Tromey
2010-07-26 9:17 ` Phil Muldoon
2010-07-26 17:07 ` Eli Zaretskii
2010-07-27 13:16 ` Phil Muldoon
2010-07-27 18:24 ` Tom Tromey
2010-07-28 9:47 ` Phil Muldoon [this message]
2010-07-30 21:39 ` Tom Tromey
2010-07-31 7:08 ` Eli Zaretskii
2010-08-03 9:55 ` Phil Muldoon
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=4C4FFCAB.4040909@redhat.com \
--to=pmuldoon@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).