Debugging with GDB Manual (5900-1473; WDB 6.2; January 2011)

breakpoints before setting new ones (see “Disabling
breakpoints” (page 53)). See “Break conditions”
(page 54).
thbreak args Set a hardware-assisted breakpoint enabled only
for one stop. args are the same as for the hbreak
command and the breakpoint is set in the same
way. However, like the tbreak command, the
breakpoint is automatically deleted after the first
time your program stops there. Also, like the
hbreak command, the breakpoint requires
hardware support and some target hardware may
not have this support. See “Disabling breakpoints”
(page 53). See also “Break conditions” (page 54).
rbreak regex Set breakpoints on all functions matching the regular
expression 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 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 'grep'. Note that this is
different from the syntax used by shells, so for
instance foo* matches all functions that include an
fo followed by zero or more os. There is an
implicit .* leading and trailing the regular
expression you supply, so to match only functions
that begin with foo, use ^foo.
When debugging C++ programs, rbreak is useful
for setting breakpoints on overloaded functions that
are not members of any special classes.
info breakpoints [n], info
break [n], info watchpoints
[n]
Print a table of all breakpoints, watchpoints, and
catchpoints set and not deleted, with the following
columns for each breakpoint:
Breakpoint Numbers,
Type
Breakpoint,
watchpoint, or
catchpoint.
Disposition Whether the
breakpoint is
marked to be
5.1 Breakpoints 49