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
Using Debug on TNS/R Processors
Debug Manual—421921-003
2-6
Setting TNS Breakpoints
instruction would be approximate. Also, multiple RISC breakpoints could map to a
single TNS instruction.
Breakpoint correspondence is illustrated in the following set of figures.
Setting TNS Breakpoints
Setting any allowable TNS breakpoint causes a corresponding breakpoint in the RISC
code. You set a TNS breakpoint by using a B command that includes a reference to a
TNS address (for example, a UC address). The PMAP command shows the allowable
TNS location with > or @ characters. How TNS breakpoints correspond to RISC
breakpoints is illustrated in Figure 2-2, which shows setting breakpoints in the user
code area.
Note. TNS breakpoints can be set only at memory-exact or register-exact points because a
corresponding RISC breakpoint can also be set. Some TNS breakpoints cannot be set at
other points because there is no corresponding RISC instruction, as illustrated in the figure
below with the double slash (//) symbol.
Figure 2-2. How TNS Breakpoints Can Correspond to RISC Breakpoints
B UC. n
+nnn
User Code Area for ProcA
B UC. n +nnn specifies a TNS breakpoint
Register-Exact Point
TNS Instructions RISC Instructions
Register-Exact PointB UC. n
+nnn
Memory-Exact Point
B UC. n
+nnn
//
//
Legend
VST0202.vsd