2.3.9. BGLOBAL

Enables or disables global breakpoints, also called processor exceptions.

Note

This command overrides the settings in the Connection Properties of the current connection. However, if you disconnect and reconnect then the settings in the Connection Properties are applied to the connection.

Syntax

BGLOBAL {,enable | ,disable} [name [;macro-call]]

BGLOBAL ,gui [;macro-call]

BGLOBAL

where:

qualifier

If no qualifier is specified, then a list of all the global breakpoints is displayed together with the current state of each breakpoint.

If specified, must be one of the following:

enable

Enable the specified global breakpoint. If name is omitted, then a list of the currently enabled global breakpoints is displayed.

disable

Disable the specified global breakpoint. If name is omitted, then a list of the currently disabled global breakpoints is displayed.

gui

Display a dialog box that enables you to select a global breakpoint to enable or disable.

Note

This qualifier has no effect when running in command line mode.

name

Identifies the global breakpoint to be enabled or disabled. See Compatibility for a list of supported names.

macro-call

Specifies a macro and any parameters it requires. This macro is run when a global breakpoint is triggered.

If the macro returns a nonzero value, execution continues. If the macro returns zero, or if you do not specify a macro, target execution stops and the debugger waits in command mode.

Description

The BGLOBAL command enables or disables global breaks. A global breakpoint is a processor event that can cause execution to halt in any application using this connection. For example, taking an undefined instruction trap might be a global breakpoint. The list of possible global breakpoint events is defined by a combination of the target processor and the Debug Interface. For more information on the meaning of the processor exceptions see the processor architecture manual.

Some simulators, including RVISS, can extend the list of possible breakpoint events beyond that defined for the processor. These extensions are normally defined by peripheral or memory models included in the simulator. For example, a memory model might define a DMA transfer event.

Each extra event is named by the model that implements it, and these names are displayed with the standard names in the GUI. You can set and modify global breakpoints for these events using the bglobal command by specifying the event name as name in the command. If the name includes spaces, you must enclose it in double quotation marks.

Note

Some processor exceptions interact with other debugger functions. For non ARMv7-M processors with the semihosting vector set to the default (0x8), you cannot enable semihosting if the SuperVisor Call (SVC) vector catch is enabled.

Compatibility

The supported events are determined in part by the currently connected processor type:

Connections to ARM hardware processors

The possible events are the exception types supported by connections to ARM processors through a hardware Debug Interface, such as DSTREAM or RealView ICE. The following options are supported for name:

reset

The RESET exception.

undef

The undefined instruction exception.

SWI

The SVC exception.

prefetch abort

The prefetch abort (instruction memory read abort) exception. You must use double quotation marks to specify this name, for example:

bglobal,enable "prefetch abort"
data abort

The data abort (data memory read or write abort) exception. You must use double quotation marks to specify this name, for example:

bglobal,enable "data abort"
IRQ

The interrupt request exception.

FIQ

The fast interrupt request exception.

RealView ARMulator ISS connections to ARM simulated processors

The possible events are the exception types supported by simulated processors on RealView ARMulator ISS connections. The following options are supported for name:

Reset

The RESET exception.

Undefined

The undefined instruction exception.

SWI

The SVC exception.

P_Abort

The prefetch abort (instruction memory read abort) exception.

D_Abort

The data abort (data memory read or write abort) exception.

Address

The address exception. Used only by the obsolete 26-bit ARM processor architectures.

IRQ

The interrupt request exception.

FIQ

The fast interrupt request exception.

ErrorP

The error exception.

Examples

The following examples show how to use BGLOBAL:

  • To disable debugger interception of the ARM architecture SVC exception, so that an application can process SVC exceptions itself, enter:

    bglobal,disable SWI
    
  • To enable debugger interception of the ARM architecture UNDEF exception, so that if the application starts executing data literals (the usual reason for unintentionally executing an undefined instruction) you can find out why, enter:

    bglobal,enable undefined
    
  • To list all global breakpoints with the current status, enter:

    bglobal
    

See also

Copyright © 2002-2011 ARM. All rights reserved.ARM DUI 0175N
Non-ConfidentialID052111