11.34 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
Breakpoint properties dialog box


Breakpoint information

The breakpoint information shows the basic properties of a breakpoint. It comprises:

Description
  • If the source file is available, the file name and line number in the file where the breakpoint is set, for example calendar.c:34.

  • 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+0x4 shows that the breakpoint is 4 bytes from the start of the main() function.

  • The address at which the breakpoint is set.

  • 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 instruction set at the breakpoint, A32 (ARM) or T32 (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, for example i==3.

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.

Type

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 the breakpoint, either Software Breakpoint or Hardware Breakpoint.

  • The instruction set of the instruction at the address of the breakpoint, A32 (ARM) or T32 (Thumb).

State

Indicates one of the following:

Active

The image or shared object containing the address of the breakpoint is loaded, and the breakpoint is set.

Disabled

The breakpoint is disabled.

No Connection

The breakpoint is in an application that is not connected to a target.

Pending

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.

Address

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.

Breakpoint options

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 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 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 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.

Silent

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.

Non-ConfidentialPDF file icon PDF versionARM DUI0446Z
Copyright © 2010-2016 ARM Limited or its affiliates. All rights reserved.