Contents|Index|Previous|Next
Deleting
breakpoints
It is often necessary to
eliminate a breakpoint, watchpoint, or catchpoint once it has done its
job and you no longer want your program to stop there. This is called deleting
the breakpoint. A breakpoint that has been deleted no longer exists; it
is forgotten.
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). When the innermost frame is selected, this is a good
way to delete a breakpoint where your program just stopped.
clearfunction
clearfilename:
function
Delete any breakpoints set
at entry to the function, function.
clearlinenum
clear filename: linenum
Delete any breakpoints set
at or within the code of the specified line, linenum.
delete [breakpoints][bnums...]
Delete the breakpoints,
watchpoints or catchpoint of the numbers specified as arguments. If no
argument is specified, delete all breakpoints (GDB asks confirmation, unless
you use the declaration,
set
confirm off).
You can abbreviate this command as d.
Top|Contents|Index|Previous|Next