Debugging with GDB Manual HP WDB v6.3 (5900-2180, August 2012)

With the clear command you can delete breakpoints according to where they are in your program.
With the delete command you can delete individual breakpoints, watchpoints, or catchpoints
by specifying their breakpoint numbers.
It is not necessary to delete a breakpoint to proceed past it. GDB automatically ignores breakpoints
on the first instruction to be executed when you continue execution without changing the execution
address.
clear Delete any breakpoints at the next instruction to be executed
in the selected stack frame (see “Selecting a frame”
(page 56)). When the innermost frame is selected, this is a
good way to delete a breakpoint where your program just
stopped.
clear function, clear
filename:function
Delete any breakpoints set at entry to the function
function.
clear linenum, clear
filename:linenum
Delete any breakpoints set at or within the code of the
specified line.
delete [breakpoints]
[range...]
Delete the breakpoints, watchpoints, or catchpoints of the
breakpoint ranges specified as arguments. If no argument
is specified, delete all breakpoints (GDB asks confirmation,
unless you have set confirm off). You can abbreviate
this command as d.
5.1.4 Disabling breakpoints
Rather than deleting a breakpoint, watchpoint, or catchpoint, you might prefer to disable it. This
makes the breakpoint inoperative as if it had been deleted, but remembers the information on the
breakpoint so that you can enable it again later.
You disable and enable breakpoints, watchpoints, and catchpoints with the enable and disable
commands, optionally specifying one or more breakpoint numbers as arguments. Use info break
or info watch to print a list of breakpoints, watchpoints, and catchpoints if you do not know
which numbers to use.
A breakpoint, watchpoint, or catchpoint can have any of four different states of enablement:
• Enabled. The breakpoint stops your program. A breakpoint set with the break command
starts out in this state.
• Disabled. The breakpoint has no effect on your program.
• Enabled once. The breakpoint stops your program, but then becomes disabled.
• Enabled for deletion. The breakpoint stops your program, but immediately after it does so it
is deleted permanently. A breakpoint set with the tbreak command starts out in this state.
You can use the following commands to enable or disable breakpoints, watchpoints, and
catchpoints:
disable [breakpoints]
[range...]
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 case the breakpoint is
enabled again later. You may abbreviate disable as dis.
enable [breakpoints]
[range...]
Enable the specified breakpoints (or all defined breakpoints).
They become effective once again in stopping your program.
enable [breakpoints] once
range...
Enable the specified breakpoints temporarily. GDB disables
any of these breakpoints immediately after stopping your
program.
44 Stopping and Continuing