Breakpoint Properties dialog box
Use the Breakpoint Properties dialog box to display the properties of a breakpoint.
It also enables you to:
Set a stop condition and an ignore count for the breakpoint.
Specify a script file to run when the breakpoint is hit.
Configure the debugger to automatically continue running on completion of all the breakpoint actions.
Assign a breakpoint action to a specific thread or processor, if available.
Figure 11-44 Breakpoint properties dialog box
The breakpoint information shows the basic properties of a breakpoint. It comprises:
If the source file is available, the file name and line number in the file where the breakpoint is set, for example
The name of the function in which the breakpoint is set and the number of bytes from the start of the function. For example,
main+0x4shows that the breakpoint is 4 bytes from the start of the
The address at which the breakpoint is set.
A breakpoint ID number,
#. In some cases, such as in a
forloop, a breakpoint might comprise a number of sub-breakpoints. These are identified as
is the number of the parent.
The instruction set at the breakpoint,
ignorecount, if set. The display format is:
countinitially, and decrements on each pass until it reaches zero.
is the value you have specified for the
hitscount that increments each time the breakpoint is hit. This is not displayed until the first hit. If you set an
hitscount does not start incrementing until the
ignorecount reaches zero.
The stop condition you have specified, for example
- Host File Location
The location of the image on the host machine.
- Compiled File Location
The path that the image was compiled with. This can be relative or absolute. This location might be different from the host file location if you compile and debug the image on different machines.
Whether or not the source file is available for the code at the breakpoint address,
Source Levelif available or
Address Levelif not available.
If the breakpoint is on code in a shared object,
Autoindicates that the breakpoint is automatically set when that shared object is loaded.
If the breakpoint is
Active, the type of the breakpoint, either
The instruction set of the instruction at the address of the breakpoint,
Indicates one of the following:
The image or shared object containing the address of the breakpoint is loaded, and the breakpoint is set.
The breakpoint is disabled.
- No Connection
The breakpoint is in an application that is not connected to a target.
The image or shared object containing the address of the breakpoint has not yet been loaded. The breakpoint becomes active when the image or shared object is loaded.
A dialog box that displays one or more breakpoint or sub-breakpoint addresses. You can use the check boxes to enable or disable the breakpoints.
The following options are available for you to set:
- Break on Selected Threads or Cores
Select this option if you want to set a breakpoint for a specific thread or processor. This option is disabled if none are available.
- Stop Condition
Specify a C-style conditional expression for the selected breakpoint. For example, to activate the breakpoint when the value of
- Ignore Count
Specify the number of times the selected breakpoint is ignored before it is activated.
The debugger decrements the count on each pass. When it reaches zero, the breakpoint activates. Each subsequent pass causes the breakpoint to activate.
- On break, run script
Specify a script file to run when the selected breakpoint is activated.Note Take care with the commands you use in a script that is attached to a breakpoint. For example, if you use the
quitcommand in a script, the debugger disconnects from the target when the breakpoint is hit.
- Continue Execution
Select this option if you want to continue running the target after the breakpoint is activated.
Controls the printing of messages for the selected breakpoint in the Commands view.
- Hardware Virtualization
Indicates whether Hardware Virtualization is supported.
- Break on Virtual Machine ID
If Hardware Virtualization is supported, specify the Virtual Machine ID (VMID) of the guest operating system to which the breakpoint applies.