You disable and enable breakpoints, watchpoints or 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 or 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. A breakpoint set with the tbreak command starts out in this state.
• Enabled for deletion

The breakpoint stops your program, but immediately after it does so it is deleted permanently.

disable [breakpoints][bnums ...]
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][bnums ...]
Enable the specified breakpoints (or all defined breakpoints). They become effective once again in stopping your program.
enable [breakpoints] once bnums...
Enable the specified breakpoints temporarily. GDB disables any of these breakpoints immediately after stopping your program.
enable [breakpoints] delete bnums...
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), breakpoints that you set are initially enabled; subsequently, they become disabled or enabled only when you use one of the previously discussed commands. (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.)