Breakpoint properties dialog box

This dialog box enables you to:

Figure 81. Breakpoint properties dialog box

Breakpoint properties dialog box

Show/hideBreakpoint information

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()+52 shows that the breakpoint is 52 bytes from the start of the accumulate() function.

  • If the source file is available, the file name and line number in the file where the breakpoint is set, threads.c:115.

  • A breakpoint ID number, #N. In some cases, such as in a for loop, a breakpoint might comprise a number of sub-breakpoints. These are identified as N.n, where N is 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, ARM or Thumb.

  • An ignore count, if set. The display format is:

    ignore = num/count

    num equals count initially, and decrements on each pass until it reaches zero.

    count is the value you have specified for the ignore count.

  • A hits count that increments each time the breakpoint is hit. This is not displayed until the first hit. If you set an ignore count, hits count does not start incrementing until the ignore count reaches zero.

  • The stop condition you have specified, (i==3).

  • 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 Unknown is displayed.


This shows:

  • whether or not the source file is available for the code at the breakpoint address, Source Level if available or Address Level if not available

  • if the breakpoint is on code in a shared object, Auto indicates that the breakpoint is automatically set when that shared object is loaded

  • if the breakpoint is Active, the type of breakpoint, either Software Breakpoint or Hardware Breakpoint

  • the type of instruction at the address of the breakpoint, ARM or Thumb.


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.

No Connection

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.


Shows true if this is a temporary breakpoint. Otherwise, shows false.

Show/hideBreakpoint options

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 x equals 10, specify x==10.

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 quit command 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)

Show/hideSee also

Copyright © 2010-2012 ARM. All rights reserved.ARM DUI 0446L