Breakpoint properties dialog box
Describes the dialog box content.
This dialog box enables you to:
display the properties of a selected breakpoint
set a conditional expression for a specific breakpoint
set an ignore counter for a specific breakpoint
specify a script file to run when the selected breakpoint is hit
enable 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 10-30 Breakpoint properties dialog box
The breakpoint information shows the basic properties of a breakpoint:
A description of the breakpoint as displayed in the Breakpoints view. This comprises:
The name of the function in which the breakpoint is set and the number of bytes from the start of the function. For example,
accumulate()+52shows that the breakpoint is 52 bytes from the start of the
If the source file is available, the file name and line number in the file where the breakpoint is set,
A breakpoint ID number,
#N. In some cases, such as in a
forloop, a breakpoint might comprise a number of sub-breakpoints. These are identified as
Nis the number of the parent. The description of a sub-breakpoint in this dialog box is shown as
main()+132sub-breakpoint ofmain()+132 @ threads.c:56 [#14 ARM] (threads)
The type of instruction at the address of the breakpoint,
ignorecount, if set. The display format is:
ignore = num/count
countinitially, and decrements on each pass until it reaches zero.
countis 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,
The name of the image.
accumulate()+52 @ threads.c:115 [#1 ARM, ignore = 3/3, 3 hits, (i==3)] (threads)
The location of the source file containing the address where the breakpoint is set, for example:
If no source file is available, then
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 breakpoint, either
the type of instruction at the address of the breakpoint,
Source Level Software Breakpoint [ARM]
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 in an application on a target that is not connected.
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 with check boxes where you can enable or disable them.
trueif this is a temporary breakpoint. Otherwise, shows
The following options are available for you to set:
- 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 counter on each pass until it reaches zero, for example:
main()+140 @ threads.c:51 [#1 ARM, ignore = 2/3] (threads)
When the value reaches zero the breakpoint activates. Each subsequent pass causes the breakpoint to activate.
Select the Reset Ignore Count option from the context menu to reset the counter to the value you have set and delay activation again.
- On break, run script
Specify a script file to run when the selected breakpoint is activated.
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 stop messages for the selected breakpoint.
- 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.
When a breakpoint activates, the debugger does the following:
displays a message in the Commands view, for example:
Execution stopped at breakpoint 1: 0x00008850 In thread 1 (OS thread id 1078) 0x00008850 51,0 thread_app_data[t].thread = t;
increments a hit count for the breakpoint, for example:
main()+140 @ threads.c:51 [#1 ARM, ignore = 0/3, 2 hits] (threads)