diff options
| author | Martin Galvan <omgalvan.86@gmail.com> | 2017-02-10 13:37:31 -0300 |
|---|---|---|
| committer | Martin Galvan <omgalvan.86@gmail.com> | 2017-02-10 13:38:54 -0300 |
| commit | 18da0c51da58527152e019924cc5105cd89765d6 (patch) | |
| tree | 6e1756a3880e3f624c6ed4e18cc0c9224f30d7ce /gdb/breakpoint.c | |
| parent | dce75bf9848c88583377c608e9734a2f8616d12b (diff) | |
| download | fsf-binutils-gdb-18da0c51da58527152e019924cc5105cd89765d6.zip fsf-binutils-gdb-18da0c51da58527152e019924cc5105cd89765d6.tar.gz fsf-binutils-gdb-18da0c51da58527152e019924cc5105cd89765d6.tar.bz2 | |
PR gdb/21122: Fix documentation mistakes for breakpoint commands
Currently, the breakpoint documentation refers to some commands taking breakpoint
"ranges" as arguments. We discussed this with Pedro and concluded that it would
be more accurate to speak in terms of breakpoint "lists", whose elements can optionally
be ranges. I also fixed a couple of minor mistakes in the docs.
gdb/ChangeLog:
* breakpoint.c (_initialize_breakpoint): Update the help description
of the 'commands' command to indicate that it takes a list argument.
gdb/doc/ChangeLog:
* gdb.texinfo (Breakpoints): Reword documentation to speak in terms of
space-separated breakpoint lists. Also add a missing @table command
and @cindex for breakpoint lists.
gdb/testsuite/ChangeLog:
* gdb.base/help.exp: Update match pattern for testing 'help commands'.
Diffstat (limited to 'gdb/breakpoint.c')
| -rw-r--r-- | gdb/breakpoint.c | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/gdb/breakpoint.c b/gdb/breakpoint.c index a76b3e4..ab6e9c8 100644 --- a/gdb/breakpoint.c +++ b/gdb/breakpoint.c @@ -16165,8 +16165,10 @@ Set ignore-count of breakpoint number N to COUNT.\n\ Usage is `ignore N COUNT'.")); add_com ("commands", class_breakpoint, commands_command, _("\ -Set commands to be executed when a breakpoint is hit.\n\ -Give breakpoint number as argument after \"commands\".\n\ +Set commands to be executed when the given breakpoints are hit.\n\ +Give a space-separated breakpoint list as argument after \"commands\".\n\ +A list element can be a breakpoint number (e.g. `5') or a range of numbers\n\ +(e.g. `5-7').\n\ With no argument, the targeted breakpoint is the last one set.\n\ The commands themselves follow starting on the next line.\n\ Type a line containing \"end\" to indicate the end of them.\n\ |