Debugging with GDB Manual The GNU Source-Level Debugger (769148-001, March 2014)

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.
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.
enable [breakpoints] delete
range...
Enable the specified breakpoints to work once, then die.
GDB deletes any of these breakpoints as soon as your
program stops there.
Except for a breakpoint set with tbreak (see “Setting breakpoints” (page 36)), breakpoints that
you set are initially enabled; subsequently, they become disabled or enabled only when you use
one of the commands above. (The command until can set and delete a breakpoint of its own,
but it does not change the state of your other breakpoints; see “Continuing and stepping” (page 45).)
Break conditions
The simplest sort of breakpoint breaks every time your program reaches a specified place. You
can also specify a condition for a breakpoint. A condition is just a Boolean expression in your
programming language (see “Expressions” (page 58)). A breakpoint with a condition evaluates
the expression each time your program reaches it, and your program stops only if the condition
is true.
Breakpoints 41