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-68
T Command
T Command
The T command traces back and displays the contents of up to 10 stack markers,
starting from the current stack marker or a designated stack marker. The T command
can either report the procedure names or translate the PC register (native mode) or the
ENV register (TNS or accelerated mode) in each stack marker. The form of the
T command is:
options
gives Debug the conditions to assume when starting the trace. The options
parameter is a list of one or more of the following, separated by commas:
[register [=]] expression
tells Debug to start the trace as though the specified register had the specified
value. If the register is a 16-bit register, only the low-order 16 bits of the
expression are used. You can include as many [register [=]] expression
specifications as are necessary to indicate where to start the trace. You can
omit register = , in which case Debug assumes the L register.
MODE { N[ATIVE] | T[NS] | A[CCELERATED] }
specifies the execution mode that Debug is to assume when starting the stack
trace. If you omit this option, Debug assumes the execution mode of the
current process.
AT expression
specifies the address of a word on the stack whose content is a native code
address. Debug assumes that this word is the return address stored by a
procedure, and attempts to begin the trace with the stack frame of that
procedure.
J 32-bit-address
specifies that the stack trace start from the context saved in a jump buffer. The
32-bit-address parameter is the RISC address of the jump buffer.
T [ & ] [ N ] [ options ] [ , [ OUT ] output-dev ]
& specifies that Debug is to begin the display with the frame immediately following
the last frame displayed. You can use this option to display successive blocks of
frames.
N specifies that Debug is to display a trace of procedure names rather than the
translated ENV or PC registers.