From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] PR python/15620, PR python/18620 - breakpoint events in Python
Date: Fri, 20 May 2016 21:18:00 -0000 [thread overview]
Message-ID: <831t4w8m3w.fsf@gnu.org> (raw)
In-Reply-To: <1463777131-7289-1-git-send-email-tom@tromey.com> (message from Tom Tromey on Fri, 20 May 2016 14:45:31 -0600)
> From: Tom Tromey <tom@tromey.com>
> Cc: Tom Tromey <tom@tromey.com>
> Date: Fri, 20 May 2016 14:45:31 -0600
>
> 2016-05-19 Tom Tromey <tom@tromey.com>
>
> PR python/15620, PR python/18620:
> * python/py-evts.c (gdbpy_initialize_py_events): Call
> add_new_registry for new events.
> * python/py-events.h (events_object) <breakpoint_created,
> breakpoint_deleted, breakpoint_modified>: New fields.
> * python/py-breakpoint.c (gdbpy_breakpoint_created): Emit the
> breakpoint changed event.
> (gdbpy_breakpoint_deleted): Emit the breakpoint deleted event.
> (gdbpy_breakpoint_modified): New function.
> (gdbpy_initialize_breakpoints): Attach to the breakpoint modified
> observer.
>
> 2016-05-20 Tom Tromey <tom@tromey.com>
>
> PR python/15620, PR python/18620:
> * python.texi (Events In Python): Document new breakpoint events.
>
> 2016-05-20 Tom Tromey <tom@tromey.com>
>
> PR python/15620, PR python/18620:
> * gdb.python/py-breakpoint.exp (connect_event, check_last_event)
> (test_bkpt_events): New procs.
OK for the documentation part.
Thanks.
next prev parent reply other threads:[~2016-05-20 21:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-20 20:45 Tom Tromey
2016-05-20 21:18 ` Eli Zaretskii [this message]
2016-07-13 13:40 ` Yao Qi
2016-07-13 19:52 ` 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=831t4w8m3w.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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