This is the mail archive of the
gdb-patches@sourceware.cygnus.com
mailing list for the GDB project.
Patch: breakpoint range doc patch
- To: gdb-patches at sourceware dot cygnus dot com
- Subject: Patch: breakpoint range doc patch
- From: Tom Tromey <tromey at cygnus dot com>
- Date: 14 Jan 2000 17:58:51 -0700
- Reply-To: tromey at cygnus dot com
I've been waiting for a reply to this patch since November 10 (I seem
to remember it being earlier than that, but the ChangeLog doesn't
lie).
Can somebody please ok this for checkin? This simply documents a
feature which has already been added to gdb. I can't imagine why it
has taken so long to get an ok for this.
Tom
Index: ChangeLog
===================================================================
RCS file: /cvs/cvsfiles/devo/gdb/doc/ChangeLog,v
retrieving revision 2.347
diff -u -r2.347 ChangeLog
--- ChangeLog 1999/11/05 19:54:59 2.347
+++ ChangeLog 1999/11/24 05:42:35
@@ -1,3 +1,9 @@
+1999-11-10 Tom Tromey <tromey@cygnus.com>
+
+ * gdb.texinfo (Breakpoints): Mention breakpoint ranges.
+ (Delete Breaks): Mention range arguments.
+ (Disabling): Likewise.
+
1999-11-05 Stan Shebs <shebs@andros.cygnus.com>
* gdb.texinfo: Clarify regular expressions used in rbreak.
Index: gdb.texinfo
===================================================================
RCS file: /cvs/cvsfiles/devo/gdb/doc/gdb.texinfo,v
retrieving revision 2.232
diff -u -r2.232 gdb.texinfo
--- gdb.texinfo 1999/11/05 19:54:59 2.232
+++ gdb.texinfo 1999/11/24 05:46:56
@@ -2100,6 +2100,14 @@
@dfn{disabled}; if disabled, it has no effect on your program until you
enable it again.
+@cindex breakpoint ranges
+@cindex ranges of breakpoints
+Some @value{GDBN} commands accept a range of breakpoints on which to
+operate. A breakpoint range is either a single breakpoint number, like
+@samp{5}, or two such numbers, in increasing order, separated by a
+hyphen, like @samp{5-7}. When a breakpoint range is given to a command,
+all breakpoint in that range are operated on.
+
@menu
* Set Breaks:: Setting breakpoints
* Set Watchpoints:: Setting watchpoints
@@ -2633,9 +2641,9 @@
@cindex delete breakpoints
@kindex delete
@kindex d
-@item delete @r{[}breakpoints@r{]} @r{[}@var{bnums}@dots{}@r{]}
-Delete the breakpoints, watchpoints, or catchpoints of the numbers
-specified as arguments. If no argument is specified, delete all
+@item delete @r{[}breakpoints@r{]} @r{[}@var{range}@dots{}@r{]}
+Delete the breakpoints, watchpoints, or catchpoints of the breakpoint
+ranges specified as arguments. If no argument is specified, delete all
breakpoints (@value{GDBN} asks confirmation, unless you have @code{set
confirm off}). You can abbreviate this command as @code{d}.
@end table
@@ -2681,7 +2689,7 @@
@kindex disable breakpoints
@kindex disable
@kindex dis
-@item disable @r{[}breakpoints@r{]} @r{[}@var{bnums}@dots{}@r{]}
+@item disable @r{[}breakpoints@r{]} @r{[}@var{range}@dots{}@r{]}
Disable the specified breakpoints---or all breakpoints, if none are
listed. A disabled breakpoint has no effect but is not forgotten. All
options such as ignore-counts, conditions and commands are remembered in
@@ -2690,15 +2698,15 @@
@kindex enable breakpoints
@kindex enable
-@item enable @r{[}breakpoints@r{]} @r{[}@var{bnums}@dots{}@r{]}
+@item enable @r{[}breakpoints@r{]} @r{[}@var{range}@dots{}@r{]}
Enable the specified breakpoints (or all defined breakpoints). They
become effective once again in stopping your program.
-@item enable @r{[}breakpoints@r{]} once @var{bnums}@dots{}
+@item enable @r{[}breakpoints@r{]} once @var{range}@dots{}
Enable the specified breakpoints temporarily. @value{GDBN} disables any
of these breakpoints immediately after stopping your program.
-@item enable @r{[}breakpoints@r{]} delete @var{bnums}@dots{}
+@item enable @r{[}breakpoints@r{]} delete @var{range}@dots{}
Enable the specified breakpoints to work once, then die. @value{GDBN}
deletes any of these breakpoints as soon as your program stops there.
@end table