Modify Breakpoint Dialog Box

Modify a breakpoint that stops program execution at a specific source code location.

With this dialog box, you can edit multiple settings of breakpoints you requested or breakpoints the debugger realizes from a 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.


Not available.

To access the Modify Breakpoint dialog box, select View > Breakpoints, right-click a breakpoint in the Breakpoints window and select Modify from the pop-up menu.


Not available.


Only available for breakpoint requests. The type of realized breakpoints is determined by the debugger and cannot be modified.

For the breakpoint type, select Breakpoint.


Only available for breakpoint requests. The location of realized breakpoints is determined by the debugger and cannot be modified.

Enter an expression into the Location field, or click Browse to browse a list of known symbols.

When the application reaches the expression, execution stops immediately. You can enter the following expressions into the Location field:

@LINE linenumber or "filename"\@LINE linenumber

A line number in the current source file or in the source file filename.

For example:

@LINE 74


"source/foo.cpp"\@LINE 74

functionname or "filename"\functionname

A function in the current source file or in the source file filename. You can click the Browse button to browse for a symbol.

For example:




An address.

For example:



When you define a condition, the debugger evaluates this condition when execution stops at the specified location. If the result is FALSE (zero), the application continues executing. In this case, an optional skip count remains unchanged. The condition can be any Boolean expression in the current language. For example: choice==2


If you want the debugger to execute a command when the program execution stops at a breakpoint, enter this command into the Action field.


When you check Continue, the application continues executing after the debugger processes the Actions list. Otherwise, it stops.

Skip Count

You can enter a positive integer as skip count number. The skip count defines the number of times a breakpoint hit is ignored. For example, a breakpoint with the skip number 2 would stop execution when encountered for the third time. First the debugger checks the condition, then the skip count number.

OK, Cancel

Click OK to create the breakpoint, or Cancel to cancel the operation.


If you want to set more than one breakpoint, click the Apply button to set a breakpoint and to leave the Set Breakpoint dialog box open.


The breakpoint should be at the beginning of the line. For example, a breakpoint at source code line 100 stops the program after line 99 executes.

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