From: Keith Seitz <keiths@redhat.com>
To: "gdb-patches@sourceware.org ml" <gdb-patches@sourceware.org>
Subject: [RFA/doc] Cleanup -break-insert documentation
Date: Wed, 20 Jun 2012 19:27:00 -0000 [thread overview]
Message-ID: <4FE22428.2090807@redhat.com> (raw)
Hi,
While working on some MI-related tasks, I had occasion to peek at the
documentation for -break-insert.
This patch does several minor things:
- it re-orders the list of options to for -break-insert to match the
order given in synopsis
- it uses "thread-id" instead of "thread" in the synopsis (to make it
more consistent with other documentation)
- it adds/documents "-p" in the list of options
Keith
doc/ChangeLog
2012-06-20 Keith Seitz <keiths@redhat.com>
* gdb.texinfo (GDB/MI Breakpoint Commands): Re-order options
for -break-insert and document -p.
Index: doc/gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.976
diff -u -p -r1.976 gdb.texinfo
--- doc/gdb.texinfo 20 Jun 2012 04:02:21 -0000 1.976
+++ doc/gdb.texinfo 20 Jun 2012 19:06:34 -0000
@@ -28020,7 +28020,7 @@ N.A.
@smallexample
-break-insert [ -t ] [ -h ] [ -f ] [ -d ] [ -a ]
[ -c @var{condition} ] [ -i @var{ignore-count} ]
- [ -p @var{thread} ] [ @var{location} ]
+ [ -p @var{thread-id} ] [ @var{location} ]
@end smallexample
@noindent
@@ -28043,10 +28043,6 @@ The possible optional parameters of this
Insert a temporary breakpoint.
@item -h
Insert a hardware breakpoint.
-@item -c @var{condition}
-Make the breakpoint conditional on @var{condition}.
-@item -i @var{ignore-count}
-Initialize the @var{ignore-count}.
@item -f
If @var{location} cannot be parsed (for example if it
refers to unknown files or functions), create a pending
@@ -28058,6 +28054,12 @@ Create a disabled breakpoint.
@item -a
Create a tracepoint. @xref{Tracepoints}. When this parameter
is used together with @samp{-h}, a fast tracepoint is created.
+@item -c @var{condition}
+Make the breakpoint conditional on @var{condition}.
+@item -i @var{ignore-count}
+Initialize the @var{ignore-count}.
+@item -p @var{thread-id}
+Restrict the breakpoint to the specified @var{thread-id}.
@end table
@subsubheading Result
next reply other threads:[~2012-06-20 19:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 19:27 Keith Seitz [this message]
2012-06-20 19:40 ` Eli Zaretskii
2012-06-20 20:12 ` Keith Seitz
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=4FE22428.2090807@redhat.com \
--to=keiths@redhat.com \
--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