1.3.43 handle

Controls the handler settings for one or more signals or exceptions. The default handler settings are dependent on the type of debug activity. For example, by default on a Linux kernel connection, all signals are handled by Linux on the target. You can use info signals to display the current settings.

When connected to an application running on a remote target using gdbserver, the debugger handles Unix signals but on bare-metal it handles processor exceptions.

Syntax

handle [name]... keyword...

Where:

name

Specifies the signal or processor exception name.

keyword

Specifies the following keywords:

noprint

Disables the print property so the occurrence of an event is not indicated at all. Using the noprint keyword implies the properties of the nostop keyword as well.

nostop

Disables the stop property so the occurrence of an event does not stop execution.

print

Enables the print property. The debugger prints a message and continues execution when the event occurs. When using gdbserver the debugger can only print if stop is enabled.

stop

Enables the stop and print properties. The debugger stops execution and prints a message when the event occurs. Using the stop keyword implies the properties of the print keyword as well.

If no name is specified then all handler settings are modified.

Example 1-46 Examples

handle SVC stop       # When an SVC exception occurs, stop execution and 
                        print a message.
handle IRQ print      # When an IRQ exception occurs, print a message, but
                        continue execution.
handle IRQ noprint    # When an IRQ exception occurs, do not print a message.
handle noprint nostop # Ignore all events and do not print a message.
Non-ConfidentialPDF file icon PDF versionARM DUI0452Z
Copyright © 2010-2016 ARM Limited or its affiliates. All rights reserved.