From: Phil Muldoon <pmuldoon@redhat.com>
To: Tom Tromey <tromey@redhat.com>, eliz@gnu.org
Cc: Doug Evans <dje@google.com>, gdb-patches@sourceware.org
Subject: Re: [patch] [python] Implement stop_p for gdb.Breakpoint
Date: Mon, 14 Mar 2011 17:56:00 -0000 [thread overview]
Message-ID: <m3bp1dhaa7.fsf@redhat.com> (raw)
In-Reply-To: <m3zkoxdcjt.fsf@fleche.redhat.com> (Tom Tromey's message of "Mon, 14 Mar 2011 08:03:34 -0600")
Tom Tromey <tromey@redhat.com> writes:
>>>>>> "Phil" == Phil Muldoon <pmuldoon@redhat.com> writes:
>
> Phil> I remember a bug about this in 2.5 that did accept const definitions
> Phil> but would later die. (And a patch was checked in. Can't remember by
> Phil> who though). Anyway, Python 2.6 rejects all of the above with:
>
> Thanks, I never remember that. It is ok without that const.
>
> Could you file a bug against Python, like Jan suggested?
>
Sure. And I have committed the code and doc patches per previous
approval. Thanks.
Should I also write something on how Parameters now have callback functions too?
Eli, Here is a NEWS patch.
Cheers,
Phil
--
diff --git a/gdb/NEWS b/gdb/NEWS
index fb36383..826bad3 100644
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -38,6 +38,10 @@
* Python scripting
+ ** Breakpoints can now be sub-classed in Python, and in particular
+ you may implement a 'stop' function that is executed each time
+ the inferior reaches that breakpoint.
+
** New function gdb.lookup_global_symbol looks up a global symbol.
** GDB values in Python are now callable if the value represents a
next prev parent reply other threads:[~2011-03-14 17:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 16:33 Phil Muldoon
2011-02-23 18:05 ` Eli Zaretskii
2011-02-24 7:02 ` Doug Evans
2011-02-24 9:50 ` Phil Muldoon
[not found] ` <AANLkTikXyH+zYkFRoUmihmDYj_nxU5648UnF5T9G-Wte@mail.gmail.com>
2011-02-28 21:19 ` Doug Evans
2011-03-07 16:43 ` Phil Muldoon
2011-03-07 20:52 ` Tom Tromey
2011-03-10 6:47 ` Doug Evans
2011-03-11 1:55 ` Tom Tromey
2011-03-11 11:59 ` Phil Muldoon
2011-03-11 18:27 ` Tom Tromey
2011-03-11 20:59 ` Doug Evans
2011-03-13 22:28 ` Phil Muldoon
2011-03-14 14:49 ` Tom Tromey
2011-03-14 17:56 ` Phil Muldoon [this message]
2011-03-14 20:01 ` Tom Tromey
2011-03-14 21:27 ` Eli Zaretskii
2011-03-11 18:36 ` Tom Tromey
2011-03-07 22:01 ` 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=m3bp1dhaa7.fsf@redhat.com \
--to=pmuldoon@redhat.com \
--cc=dje@google.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