From: Eli Zaretskii <eliz@gnu.org>
To: Phil Muldoon <pmuldoon@redhat.com>
Cc: simon.marchi@ericsson.com, keiths@redhat.com, gdb-patches@sourceware.org
Subject: Re: [python] Allow explicit locations in breakpoints.
Date: Fri, 08 Dec 2017 13:50:00 -0000 [thread overview]
Message-ID: <83h8t1wcqd.fsf@gnu.org> (raw)
In-Reply-To: <e49784e0-bdac-6e98-fafd-8b8bff59fda2@redhat.com> (message from Phil Muldoon on Thu, 7 Dec 2017 10:02:44 +0000)
> From: Phil Muldoon <pmuldoon@redhat.com>
> Date: Thu, 7 Dec 2017 10:02:44 +0000
>
> diff --git a/gdb/NEWS b/gdb/NEWS
> index 9246659bfb..592fe70156 100644
> --- a/gdb/NEWS
> +++ b/gdb/NEWS
> @@ -24,6 +24,9 @@
> gdb.new_thread are emitted. See the manual for further
> description of these.
>
> + ** Python breakpoints can now accept explicit locations. See the
> + manual for a further description of this feature.
^^^^^^^^^
"the detailed"?
Otherwise the documentation parts are okay. Thanks.
next prev parent reply other threads:[~2017-12-08 13:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <04ccc2c4-7827-eedc-d8db-a83a0167acb6@redhat.com>
2017-08-23 17:51 ` Keith Seitz
2017-08-23 18:31 ` Phil Muldoon
2017-10-16 18:23 ` Simon Marchi
2017-10-16 18:33 ` Simon Marchi
2017-10-16 20:24 ` Phil Muldoon
2017-10-16 21:26 ` Simon Marchi
2017-10-16 22:01 ` Phil Muldoon
2017-10-16 22:26 ` Simon Marchi
2017-11-17 11:02 ` Phil Muldoon
2017-11-17 13:31 ` Eli Zaretskii
2017-11-17 14:02 ` Phil Muldoon
2017-11-23 22:17 ` Simon Marchi
2017-11-24 14:07 ` Phil Muldoon
2017-12-07 10:02 ` Phil Muldoon
2017-12-07 12:16 ` Phil Muldoon
2017-12-07 14:54 ` Simon Marchi
2017-12-07 15:12 ` Phil Muldoon
2017-12-07 16:41 ` Simon Marchi
2017-12-08 13:50 ` Eli Zaretskii [this message]
2017-09-12 10:03 ` Phil Muldoon
2017-10-02 15:18 ` Phil Muldoon
2017-10-16 11:14 ` Phil Muldoon
2017-10-16 18:31 ` Simon Marchi
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=83h8t1wcqd.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=keiths@redhat.com \
--cc=pmuldoon@redhat.com \
--cc=simon.marchi@ericsson.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