From: Yao Qi <yao@codesourcery.com>
To: <gdb-patches@sourceware.org>, Eli Zaretskii <eliz@gnu.org>
Subject: Re: [PATCH] Fix PR14371: doc on =breakpoint-deleted
Date: Mon, 06 Aug 2012 14:23:00 -0000 [thread overview]
Message-ID: <1487308.mLOQtHcNVu@qiyao.dyndns.org> (raw)
In-Reply-To: <83fw83b0kh.fsf@gnu.org>
On Saturday, August 04, 2012 10:03:58 AM Eli Zaretskii wrote:
> > -breakpoint commands; @xref{GDB/MI Breakpoint Commands}.
> > +breakpoint commands; @xref{GDB/MI Breakpoint Commands}. The @var{id}
> > +argument is the id of the breakpoint. ^^^^^^^^
>
> ^^^^^^^^^^^^^^^^^^^^^^^^
> Not "@var{id}", but "@var{number}", for consistency with the
> description above. Also, I'd prefer "the ordinal number of the
> breakpoint" instead of the end of the last sentence, because "id of
> the breakpoint" doesn't really say what it is.
>
"number" of breakpoint is used other places in doc. Fixed as you suggested.
> OK with those changes.
Applied.
--
Yao (齐尧)
gdb/doc:
2012-08-06 Yao Qi <yao@codesourcery.com>
Fix PR14371.
* gdb.texinfo (GDB/MI Async Records): Fix the doc for
'=breakpoint-deleted'.
---
gdb/doc/gdb.texinfo | 5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index b7b15ec..9f9fe40 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -27609,13 +27609,14 @@ thread groups.
@item =breakpoint-created,bkpt=@{...@}
@itemx =breakpoint-modified,bkpt=@{...@}
-@itemx =breakpoint-deleted,bkpt=@{...@}
+@itemx =breakpoint-deleted,id=@var{number}
Reports that a breakpoint was created, modified, or deleted,
respectively. Only user-visible breakpoints are reported to the MI
user.
The @var{bkpt} argument is of the same form as returned by the various
-breakpoint commands; @xref{GDB/MI Breakpoint Commands}.
+breakpoint commands; @xref{GDB/MI Breakpoint Commands}. The
+@var{number} is the ordinal number of the breakpoint.
Note that if a breakpoint is emitted in the result record of a
command, then it will not also be emitted in an async record.
--
1.7.7.6
prev parent reply other threads:[~2012-08-06 14:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-04 4:05 Yao Qi
2012-08-04 7:04 ` Eli Zaretskii
2012-08-06 14:23 ` Yao Qi [this message]
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=1487308.mLOQtHcNVu@qiyao.dyndns.org \
--to=yao@codesourcery.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/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