diff options
| author | Jason Molenda <jmolenda@apple.com> | 1999-11-09 01:23:30 +0000 |
|---|---|---|
| committer | Jason Molenda <jmolenda@apple.com> | 1999-11-09 01:23:30 +0000 |
| commit | 11cf87416416e13eff634a70b4954fe6a3912720 (patch) | |
| tree | a6dc7a21bb3d45b89c3f95e4b5862ec9d2fab83b /gdb/doc | |
| parent | 98007ce7b0dea06f0c04d833d39b5a9c9773a07a (diff) | |
| download | gdb-11cf87416416e13eff634a70b4954fe6a3912720.zip gdb-11cf87416416e13eff634a70b4954fe6a3912720.tar.gz gdb-11cf87416416e13eff634a70b4954fe6a3912720.tar.bz2 | |
import gdb-1999-11-08 snapshot
Diffstat (limited to 'gdb/doc')
| -rw-r--r-- | gdb/doc/ChangeLog | 4 | ||||
| -rw-r--r-- | gdb/doc/gdb.texinfo | 19 |
2 files changed, 16 insertions, 7 deletions
diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog index cfb80b4..45e1cdb 100644 --- a/gdb/doc/ChangeLog +++ b/gdb/doc/ChangeLog @@ -1,3 +1,7 @@ +1999-11-05 Stan Shebs <shebs@andros.cygnus.com> + + * gdb.texinfo: Clarify regular expressions used in rbreak. + 1999-10-15 Kevin Buettner <kevinb@cygnus.com> * gdbint.texinfo (MEMORY_INSERT_BREAKPOINT, diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index 316d58c..b4ad4e3 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -2229,14 +2229,19 @@ See also @ref{Conditions, ,Break conditions}. @kindex rbreak @cindex regular expression @item rbreak @var{regex} -@c FIXME what kind of regexp? Set breakpoints on all functions matching the regular expression -@var{regex}. This command -sets an unconditional breakpoint on all matches, printing a list of all -breakpoints it set. Once these breakpoints are set, they are treated -just like the breakpoints set with the @code{break} command. You can -delete them, disable them, or make them conditional the same way as any -other breakpoint. +@var{regex}. This command sets an unconditional breakpoint on all +matches, printing a list of all breakpoints it set. Once these +breakpoints are set, they are treated just like the breakpoints set with +the @code{break} command. You can delete them, disable them, or make +them conditional the same way as any other breakpoint. + +The syntax of the regular expression is the standard one used with tools +like @file{grep}. Note that this is different from the syntax used by +shells, so for instance @code{foo*} matches all functions that include +an @code{fo} followed by zero or more @code{o}s. There is an implicit +@code{.*} leading and trailing the regular expression you supply, so to +match only functions that begin with @code{foo}, use @code{^foo}. When debugging C++ programs, @code{rbreak} is useful for setting breakpoints on overloaded functions that are not members of any special |