Red Hat ENTERPRISE LINUX 4 - DEVELOPER TOOLS GUIDE, Manual

Page: 52 / 410

42 Chapter 7. Stopping and Continuing
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 (refer
to Section 8.3 Selecting a frame ). 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 argu-
ments. If no argument is specified, delete all breakpoints (gdb asks confirmation, unless you have
set confirm off
). You can abbreviate this command as
d
.
7.1.5. 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
.