Debug Manual

Debug Commands
Debug Manual—421921-003
4-66
R Command
Considerations
•
The PRV ON command requires that the process you are debugging be executing
under the local super ID (255, 155). After you specify the PRV ON command, you
can enter any of the privileged commands or options.
•
Privileged debugging is never available automatically. Before using the privileged
Debug commands and options, you must always issue the PRV ON command; the
security subsystem then decides whether you have the proper access to be
granted privileged debugging. The only exception is where a process falls into a
debugging session that is already privileged because of an earlier PRV ON
command from Debug (or a SET PRIV MODE ON command from Inspect) during
the life of the process.
•
The privileged Debug commands are:
°
The FREEZE, HALT, PRV, V, and VQA commands
°
Access data and code in the kernel address space (Kseg0 and Kseg2).
°
Plant code breakpoints in code containing PRIV or CALLABLE procedures,
including licensed UC, UL, UCr, SRLs, or system code and library.
°
Commands that modify user code.
Example
For examples that use the R command, see Appendix F, Sample Debug Sessions.
R Command
The R command causes the application process to leave the debug state and resume
execution.
You can specify a conditional resume. For a conditional resume, Debug executes the
R command only if the specified relation between the two expressions is true. A
conditional resume is particularly useful to include in a command string on an execute
code breakpoint or execute memory-access breakpoint.
The form of the R command is:
expression-1
is a 16-bit word expression.
R [ expression-1 op expression-2 ]