From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA 7/8] Allow breakpoint commands to be set from Python
Date: Thu, 19 Apr 2018 19:31:00 -0000 [thread overview]
Message-ID: <83efjbyovj.fsf@gnu.org> (raw)
In-Reply-To: <20180419191539.661-8-tom@tromey.com> (message from Tom Tromey on Thu, 19 Apr 2018 13:15:38 -0600)
> From: Tom Tromey <tom@tromey.com>
> Cc: Tom Tromey <tom@tromey.com>
> Date: Thu, 19 Apr 2018 13:15:38 -0600
>
> This changes the Python API so that breakpoint commands can be set by
> writing to the "commands" attribute.
>
> 2018-04-19 Tom Tromey <tom@tromey.com>
>
> PR python/22731:
> * NEWS: Mention that breakpoint commands are writable.
> * python/py-breakpoint.c (bppy_set_commands): New function.
> (breakpoint_object_getset) <"commands">: Use it.
>
> doc/ChangeLog
> 2018-04-19 Tom Tromey <tom@tromey.com>
>
> PR python/22731:
> * python.texi (Breakpoints In Python): Mention that "commands" is
> writable.
>
> testsuite/ChangeLog
> 2018-04-19 Tom Tromey <tom@tromey.com>
>
> PR python/22731:
> * gdb.python/py-breakpoint.exp: Test setting breakpoint commands.
OK for the documentation parts.
Thanks.
next prev parent reply other threads:[~2018-04-19 19:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-19 19:16 [RFA 0/8] Various command-related improvements Tom Tromey
2018-04-19 19:16 ` [RFA 1/8] Allocate cmd_list_element with new Tom Tromey
2018-04-19 19:16 ` [RFA 2/8] Use counted_command_line everywhere Tom Tromey
2018-04-24 16:43 ` Pedro Alves
2018-04-24 23:11 ` Tom Tromey
2018-04-24 23:18 ` Tom Tromey
2018-04-19 19:16 ` [RFA 8/8] Let gdb.execute handle multi-line commands Tom Tromey
2018-04-19 19:32 ` Eli Zaretskii
2018-04-24 16:44 ` Pedro Alves
2018-04-19 19:16 ` [RFA 3/8] Make print_command_trace varargs Tom Tromey
2018-04-24 16:43 ` Pedro Alves
2018-04-19 19:16 ` [RFA 5/8] Allow defining a user command inside a user command Tom Tromey
2018-04-24 16:43 ` Pedro Alves
2018-04-24 23:24 ` Tom Tromey
2018-04-19 19:16 ` [RFA 7/8] Allow breakpoint commands to be set from Python Tom Tromey
2018-04-19 19:31 ` Eli Zaretskii [this message]
2018-04-24 16:43 ` Pedro Alves
2018-04-19 19:16 ` [RFA 4/8] Constify prompt argument to read_command_lines Tom Tromey
2018-04-24 16:43 ` Pedro Alves
2018-04-19 19:16 ` [RFA 6/8] Use function_view in cli-script.c Tom Tromey
2018-04-22 19:02 ` Pedro Alves
2018-04-24 23:38 ` 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=83efjbyovj.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