| Copyright © 2002-2009 ARM Limited. All rights reserved. | ARM DUI 0153K |
| Non-Confidential | |
 PDF version | |
| Home > Using Macros for Debugging > About using macros for debugging > What is a macro? |
| |||
| Home > Using Macros for Debugging > About using macros for debugging > What is a macro? | |||
Macros are:
interpreted C code running on the host with access to target memory and symbols
user-defined debugger symbols (in host or target memory)
debugger functions.
Macros can access debugger variables, external windows and programs, and can be attached to breakpoints, aliases, and windows.
A macro can contain:
a sequence of expressions
string formatting controls
statements
calls to other macros
predefined macros
target functions
debugger commands.
You can define and use macros at any time during a debugging session to use the commands or statements contained in the macro. You call the macro with a single command using the name. The macro definition might contain parameters that you change each time the macro is called.
When a macro is defined, you can use it as:
a complex command or in an expression
an attachment to the GO command, or with the GOSTEP command
an attachment to a breakpoint to create breakpoint condition testing
an attachment to a user-defined window or file where the macro can send information.
the following in the RealView Debugger Command Line Reference Guide:
Alphabetical command reference for details of the GO and GOSTEP commands
| Copyright © 2002-2009 ARM Limited. All rights reserved. | ARM DUI 0153K |
| Non-Confidential | |
| PDF version | |
| Home > Using Macros for Debugging > About using macros for debugging > What is a macro? |