Breakpoint Tables

As breakpoints are defined, they are recorded in a breakpoint table associated with the current program. You can display and modify this table in certain limited ways.

breakpoint_table_command

        : show_all_breakpoints_command

        | delete_breakpoint_command

        | enable_breakpoint_command

        | disable_breakpoint_command

Each entry in the breakpoint table has the following properties:

• A unique breakpoint number that is used to identify and refer to that breakpoint.
• An event description that characterizes the circumstances under which the breakpoint triggers.
• Actions (a possibly empty list of debugger commands) to be performed when the breakpoint triggers.
• A final disposition: either continue or break (stop).
• Enabled and disabled states.

In addition to the main effects of a breakpoint definition, as discussed in Breakpoint Definitions, a breakpoint definition also sets the debugger variable $lasteventmade to the breakpoint number of the breakpoint just defined. This value can be recalled for later use if desired. For example:

(idb) stop in List<Node>::append

[#2: stop in void List<Node>::append(class Node* const)]

(idb) cont

[2] stopped at [void List<Node>::append(class Node* const):148 0x0804c55e]

    148     if (!_firstNode)

(idb) print $lasteventmade

2

(idb) set $my_break = $lasteventmade

(idb) print $my_break

2

If an error occurs in a breakpoint command, the variable $lasteventmade is not changed.