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.
Type |
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 or Thread Syncpoint. Use thread syncpoints to synchronize a set of threads. The breakpoint creates a thread barrier. When any thread in a thread set reaches this barrier, it is frozen, and the debugger ignores any attempt to step or continue execution, until all other threads in the thread set have reached the barrier. The program execution remains stopped at the breakpoint until you continue the program. If you manually stop execution before all threads in the thread set have reached the barrier, the debugger continues to hold all threads in the thread set until all of them reach the thread syncpoint. |
||||||
Location |
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. See also Symbol Selector Dialog Box: Simple Search Tab. When the application reaches the expression, execution stops immediately. You can enter the following expressions into the Location field:
|
||||||
Condition |
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 |
||||||
Action |
If you want the debugger to execute a command when the program execution stops at a breakpoint, enter this command into the Action field. |
||||||
Continue |
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. |
||||||
Thread Filter |
Not available for realized thread syncpoints. In this case the thread filter is determined by the debugger and cannot be modified. When you specify one or more threads or thread sets in this field, execution stops when any of the threads you specify triggers the breakpoint. Specify thread IDs with integer values, as shown in the Threads window. Separate multiple thread IDs with commas. To specify thread sets, use thread set notation. Alternatively, click Browse to select one or more thread sets. |
||||||
Stopping Threads |
When you specify one or more threads or thread sets in this field, execution stops in all of the threads you specify when the breakpoint is triggered. Specify thread IDs with integer values, as shown in the Threads window. Separate multiple thread IDs with commas. To specify thread sets, use the following syntax: t:[start_id:end_id]. Alternatively, click Browse to select one or more thread sets. |
||||||
OK, Cancel |
Click OK to create the breakpoint, or Cancel to cancel the operation. |
||||||
Apply |
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.
Copyright © 2001-2011, Intel Corporation. All rights reserved.