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-14
Set Trace Code Breakpoint
locations and the Q-mode syntax is not allowed. If start-address is an N mode
address, start-address refers to a 32-bit variable.
?
means list.
count
is an expression indicating the number of 16-bit words to be displayed. The value
is stored in 32 bits if a TNS/R register or N-mode start-address is used;
otherwise, it is stored in 16 bits. If count is stored in 32 bits, only the value in the
lower-order 16 bits are used to determine the number of 16-bit words to be
displayed.
If a TNS stack register R0 through R7 is specified, the value for count has to be 1
in order to display the 16-bit contents of the register. To display a range of the
stack registers, enter the starting register and count values. For example, to
display all eight stack registers, enter R0?#8.
If a TNS/R register is specified, the value for count has to be 2 in order to display
the 32-bit contents of register as two 16-bit values. To display a range of the
TNS/R registers, enter the starting register and count values. For example, to
display all 32 registers, enter $00?#64.
ALL
For more information on the description of this option, see Set Unconditional Code
Breakpoint on page 4-7.
Considerations
•
Debug displays this header each time the breakpoint location is executed:
°
TNS and accelerated modes
TRACE code-address, space-identifier
This header gives the address where the break occurred. In TNS or
accelerated mode, code-address is a C-relative address, which gives the
address of the break relative to the identified TNS code segment. An r in the
space-identifier, instead of a segment index, indicates native code; that
is, SCr, SLr, and so forth. (UC appearing without a segment index is
equivalent to UCr.)
°
RISC
TRACE $PC=code-address
In native mode, code-address is a 32-bit hexadecimal value.