Managing breakpoints.
Sébastien Granjoux
seb.sfo@free.fr
Philip Chimento
philip.chimento@gmail.com

# Eten-puntuak

Breakpoints are used to stop the execution of the program at a particular point so that the state of the program can be examined at those locations.

# Listing breakpoints

From the main menu, select View Breakpoints to open the Breakpoint window.

This view has the following columns:

## Location

This is the position of the breakpoint in the source file. When the breakpoint is set by the debugger, you can get additional information such as the function containing the breakpoint.

## Address

This field is filled with the address of the breakpoint when it is set by the debugger.

## Type

This always displays breakpoint. It will be used in a future release supporting different kinds of breakpoints.

## Condition

This is the breakpoint condition. It is empty if no condition is defined.

## Pasaldi kopurua

When the debugger is not running, this column displays the pass count of the breakpoint, or zero if it is not defined.

When the debugger is running, if the pass count is zero, this column displays the number of times this breakpoint has been triggered. If the pass count is not zero, both numbers are displayed. The pass count is the second number.

## State

This is the state of the breakpoint. It may be

## Pending:

the breakpoint is not set in your program.

## Permanent:

the breakpoint is set (its id number is displayed in parentheses).

## Temporary:

the breakpoint is set but will be deleted if reached.

All breakpoints are kept across Anjuta sessions even if they correspond to a non-existing locations, for example in a source file of a shared library not loaded yet. In this case their states are set as pending.

# Setting breakpoints

From the main menu, select Debug Add Breakpoint... or right click in the Breakpoint window and select Add Breakpoint....

Fill in the Location, which is the position of the breakpoint, and the other fields if desired. If a file is currently opened in the editor, the Location defaults to the current line. See for more information.

Another solution is to use the toggle breakpoint function. If there is no breakpoint on the current line, it will add one. Otherwise, it will remove it.

From the main menu, select Debug Toggle Breakpoint or right click in the Editor window and select Toggle Breakpoint.

# Editing breakpoints

You can't change the location of a breakpoint; create a new breakpoint instead. However, you can change the break condition or the pass count. To edit a breakpoint:

Select a breakpoint in the Breakpoint window.

Right click in the Breakpoint window and select Edit Breakpoint....

Change the Condition or Pass Count fields and click on OK when you are done. See for more information.

# Removing breakpoints

You can remove a breakpoint using the toggle breakpoint function described above. However, if you want to remove more than one breakpoint or the breakpoint is in a different file than the one you are editing, you can use the breakpoint window:

Select a breakpoint in the Breakpoint window.

Right click in the Breakpoint window and select Remove Breakpoint.

To remove all breakpoints:

From the main menu, select Debug Remove All Breakpoints or right-click in the Breakpoint window and select Remove All Breakpoints.

# Enabling and disabling breakpoints

Sometimes you might want to disable a breakpoint temporarily instead of deleting it altogether. To disable or re-enable a breakpoint:

Click on the Enable checkmark in the Breakpoint window or right click in the Breakpoint window and select Enable Breakpoint or Disable Breakpoint.

You can disable all breakpoints using:

From the main menu, select Debug Disable All Breakpoints or right-click in the Breakpoint window and select Disable All Breakpoints.