Debug Manual
Table Of Contents
- What’s New in This Manual
- About This Manual
- 1 Introduction
- Execution Modes on TNS/R Systems
- What User Access Is Required for Debugging
- How to Make a Process Enter Debug
- How to Select Debug as the Debugger
- Why a Process Enters Debug
- How to Determine Process State on a Trap or Signal
- Ending a Debug Session
- What Appears in the Debug Header Message
- How to Use Debug
- How Debug Breakpoints Work
- 2 Using Debug on TNS/R Processors
- 3 Debug Command Overview
- 4 Debug Commands
- Command Summary
- A Command
- AMAP Command
- B Command
- BASE Command
- BM Command
- C Command
- CM Command
- D Command
- DJ Command
- DN Command
- EX[IT] Command
- F[ILES] Command
- FC Command
- FN Command
- FNL Command
- FREEZE Command
- HALT Command
- H[ELP] Command
- I Command
- IH Command (TNS/R Native and OSS Processes)
- INSPECT Command
- LMAP Command
- M Command
- MH Command (TNS/R Native and OSS Processes)
- P[AUSE] Command
- PMAP Command (Accelerated Programs)
- PRV Command
- R Command
- S[TOP] Command
- T Command
- V Command
- VQ Command
- VQA Command
- = Command
- ? Command
- A Error Messages
- B ASCII Character Set
- C Command Syntax Summary
- Register Syntax
- Expression Syntax
- Address Syntax
- A Command
- AMAP Command
- B Command
- BASE Command
- BM Command
- C Command
- CM Command
- D Command
- DJ Command
- DN Command
- EX[IT] Command
- F[ILES] Command
- FC Command
- FN Command
- FNL Command
- FREEZE Command
- HALT Command
- H[ELP] Command
- I Command
- IH Command
- INSPECT Command
- LMAP Command
- M Command
- MH Command
- Output-Device Syntax
- P[AUSE] Command
- PMAP Command
- PRV Command
- R Command
- S[TOP] Command
- T Command
- V Command
- VQ Command
- VQA Command
- = Command
- ? Command
- D Session Boundaries
- E Correspondence Between Debug and Inspect Commands
- F Sample Debug Sessions
- Glossary
- Index

Debug Commands
Debug Manual—421921-003
4-64
PMAP Command (Accelerated Programs)
PMAP Command (Accelerated Programs)
The PMAP command prints corresponding blocks of TNS and RISC instruction code.
The form of the PMAP command is:
address
is a code address. For more information, see Address Syntax on page 3-12. The
address-mode parameters allowed for a code address are as follows:
•
UC, UL, SL, and C address modes are allowed while in nonprivileged mode.
N address mode is also allowed for addresses in any native code space and
for addresses in accelerated code spaces UC, UL, and SL.
•
Any address mode appropriate for the processor is allowed while in privileged
mode.
count
is an expression representing the number of instructions to be displayed. Valid
values for count are integers. Debug displays the minimum number of blocks of
instructions that includes the count number of instructions.
[OUT] output-dev
specifies where the display is directed. Debug output can be directed to an output
device, a process, or a spooler collector. Debug output cannot be directed to a disk
file. If you omit output-dev, Debug assumes the home terminal.
output-dev has these formats.
Syntax for a device other than a disk:
[ node.]{device-name[.qualifier ] }
{ldev-number }
Syntax for a named process:
[ node.]process-name[:seq-no][.qual-1[.qual-2] ]
Syntax for an unnamed process:
[ node.]$:cpu:pin:seq-no
•
For syntax descriptions of these process and device names, see the Guardian
Procedure Calls Reference Manual.
Considerations
•
The PMAP command is allowed only on TNS or RISC code in accelerated program
areas.
PMAP address [ , count ] [ , [ OUT ] output-dev ]