Breakpoints Window

Display information on all existing breakpoints.

Menu

View > Breakpoints

Toolbar

Breakpoints

The Breakpoints window displays a list of all breakpoints that are currently set. You can use the window to set, delete, modify, enable, or disable breakpoints. The window displays the breakpoint with an icon that indicates the breakpoint's type and state and provides information on breakpoint IDs, hit counts, conditions, locations, and threads.

Icon Breakpoint Type State
Code breakpoint Enabled
Code breakpoint Disabled
Code breakpoint Pending
Data breakpoint Enabled
Data breakpoint Disabled
Platform breakpoint Enabled
Platform breakpoint Disabled

The window displays your breakpoint requests and their actual realizations by the debugger. Your breakpoint request holds all information you specified for the breakpoint. You can set, modify, and delete those requests in the Breakpoints window as you like. Modifying a breakpoint request affects the realized breakpoints. For example, when you disable a breakpoint request, the debugger does not realize any breakpoints for this request.

For the majority of your use cases, only one breakpoint would be realized for a breakpoint request. For those breakpoints, the breakpoint information is displayed in-line with the breakpoint request. This behavior is called folding. In this case, only the ID number of the request is displayed while all other information in this line refers to the actually realized breakpoint. When you modify or delete a folded breakpoint, the changes are applied to the breakpoint request as well.

Enable or disable a breakpoint by checking or unchecking its checkbox.

The Breakpoints window displays all your breakpoints in a table. See the following screenshot for an example:

Code Breakpoints

For code breakpoints, the columns contain the following information:

Column

Definition

Id

Contains a checkbox, the ID number of the breakpoint, and the icon of the breakpoint. You can use the checkbox to toggle the state of the breakpoint (enabled or disabled). The icon reflects the type and state of the breakpoint.

Address

Location of the breakpoint in the assembler source code.

Function

Name of the function the breakpoint is located in.

File

Name of the file and line number where the breakpoint is located.

Skip Count

Indicates how many times the debugger skips this breakpoint until it stops execution. That is, whenever the debugger hits this breakpoint, Skip Count decrements by one until it reaches zero. Then execution halts, and Skip Count resets to the Skip value of the breakpoint.

Condition

Condition that must be satisfied for the execution to halt, or for other specified actions to execute.

Action

List of actions that the debugger executes upon reaching the breakpoint, provided that the Condition is satisfied and the Skip Count is not zero. Note that continue actions are also displayed in this list.

HW Id

If this breakpoint is a hardware breakpoint, shows the ID number of the hardware breakpoint.

Symbol

Symbolic name of the breakpoint. You can use this name to refer to the breakpoint in debugger commands.

Data Breakpoints

For data breakpoints, the columns contain the following information:

Column

Definition

Id

Contains a checkbox, the ID number of the breakpoint, and the icon of the breakpoint. You can use the checkbox to toggle the state of the breakpoint (enabled or disabled). The icon reflects the type and state of the breakpoint.

Address

Location of the beginning of the monitored memory region.

Skip Count

Indicates how many times the debugger skips this breakpoint until it stops execution. That is, whenever the debugger hits this breakpoint, Skip Count decrements by one until it reaches zero. Then execution halts, and Skip Count resets to the Skip value of the breakpoint.

Condition

Condition that must be satisfied for the execution to halt, or for other specified actions to execute.

Action

List of actions that the debugger executes when the breakpoint triggers, provided that the Condition is satisfied and the Skip Count is not zero. Note that continue actions are also displayed in this list.

HW Id

ID number of the hardware breakpoint.

Addition

Contains a string of the following format:

len=<l>, acc=<a>, mask=<m>,

where <l> is the size of the monitored memory region in bytes and <a> is the type of access that triggers the breakpoint.

Symbol

Symbolic name of the breakpoint. You can use this name to refer to the breakpoint in debugger commands.

Platform Breakpoints

For platform breakpoints, the columns contain the following information:

Column

Definition

Id

Contains a checkbox, the ID number of the breakpoint, and the icon of the breakpoint. You can use the checkbox to toggle the state of the breakpoint (enabled or disabled). The icon reflects the type and state of the breakpoint.

Function

Type of the platform breakpoint.

Skip Count

Indicates how many times the debugger skips this breakpoint until it stops execution. That is, whenever the debugger hits this breakpoint, Skip Count decrements by one until it reaches zero. Then execution halts, and Skip Count resets to the Skip value of the breakpoint.

Condition

Condition that must be satisfied for the execution to halt, or for other specified actions to execute.

Action

List of actions that the debugger executes when the breakpoint triggers, provided that the Condition is satisfied and the Skip Count is not zero. Note that continue actions are also displayed in this list.

Symbol

Symbolic name of the breakpoint. You can use this name to refer to the breakpoint in debugger commands.

Pop-up Menu

Create...

Creates a new breakpoint. You can only request a breakpoint. The debugger interprets the requested settings. If the breakpoint is realizable, it creates one or more breakpoints matching the request. Unrealized breakpoints are displayed with a yellow triangle icon in the Breakpoints window or as <PENDING> in the Console window.

Modify...

Opens the Modify Breakpoint dialog box. Use this dialog box to change the settings of the selected breakpoint.

Note

Modifying one of multiple breakpoints at a location does not modify the other related realized breakpoints or the breakpoint request. If you modify a realized breakpoint, be aware that the debugger can dynamically remove breakpoints or realize new ones and the changes will probably be lost in these cases. This means, to change the breakpoints permanently, you would have to modify your breakpoint request.

Enable Selected

Enables the selected breakpoints.

Disable Selected

Disables the selected breakpoints. Disabled breakpoints still exist, but execution does not stop at them. Disabling one of multiple breakpoints at a location does not disable other related breakpoints or the breakpoint request. Disabling a breakpoint request disables all breakpoints the debugger realized from it and no new breakpoints are realized.

Delete Selected

Deletes the selected breakpoint. Deleting a breakpoint request deletes all breakpoints the debugger realized from it.

Note

When you delete one of multiple breakpoints at a location, the debugger can dynamically realize new breakpoints at this location when the settings of the breakpoint request are met again.

Jump To Source

Sets the view in the Source window to the position of the selected breakpoint. Note that this item is only available for code breakpoints.

Jump To Assembler

Sets the view in the Assembler window to the position of the selected breakpoint. Only available for code breakpoints.

Show Memory

Opens a Memory window displaying the memory of the selected breakpoint. Only available for data breakpoints.

Enable All

Enables all breakpoints.

Disable All

Disables all existing breakpoints. The breakpoints still exist, but execution does not stop at them.

Delete All

Deletes all breakpoints.

Copy

Copies the selected breakpoints.

Copy All

Copies all breakpoints.

Select All

Selects all breakpoints.

For more complete information about compiler optimizations, see our Optimization Notice.