Table of Contents
Advertisement
Chapter 6: Using Macros and Command Files
Using Macros
}
...
If a macro is executed while the PC is pointing into the function foo(),
variables i, j, and k can be directly accessed. If this is not the case, i must be
accessed with a module qualifier, such as init\i. The function static j must be
accessed as init\foo\j. The automatic k can be accessed as init\foo\k if the stack
frame for foo() is alive.
Macro control flow statements
Macros support the following C control flow statements:
•
•
•
•
However, macros cannot contain conditional expressions of the form:
<expression>?<expression>:<expression>
Macro return values
Macros support the C "return" statement for returning values.
If a breakpoint macro returns a nonzero value, program execution continues.
If it returns a zero value, program execution is halted. If a macro does not
return a value, it should be declared as void when it is defined.
Macros containing debugger commands
You can create macros that contain only a sequence of debugger commands.
Macros containing only debugger commands are similar to command files.
You can use these macros to set up complex initialization conditions.
You cannot use the following commands in macros:
•
•
•
•
•
•
•
190
If-else
While and For
Do-while
Break and Continue in While, For, and Do statements.
Program Run
Program Step
Program Step Over
Debugger Host_Shell
Debugger Macro Add
Symbol Add
Symbol Remove
Advertisement
Table of Contents
