This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/21122] New: Documentation mistakes for breakpoint-related commands
- From: "martingalvan at sourceware dot org" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Thu, 09 Feb 2017 18:06:06 +0000
- Subject: [Bug gdb/21122] New: Documentation mistakes for breakpoint-related commands
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=21122
Bug ID: 21122
Summary: Documentation mistakes for breakpoint-related commands
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: martingalvan at sourceware dot org
Target Milestone: ---
The current documentation states the following:
"Some gdb commands accept a range of breakpoints on which to operate. A
breakpoint range is either a single breakpoint number, like ‘5’, or two such
numbers, in increasing order, separated by a hyphen, like ‘5-7’. When a
breakpoint range is given to a command, all breakpoints in that range are
operated on."
However, this fails to mention that ranges can also be specified as
space-separated lists of breakpoint numbers, like '5 6 7'.
On a related issue, 'help commands' seems to imply that the 'commands' command
can only be applied to a single breakpoint at the time:
(gdb) help commands
Set commands to be executed when a breakpoint is hit.
Give breakpoint number as argument after "commands".
...
--
You are receiving this mail because:
You are on the CC list for the bug.