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-16
Display Breakpoints
ALL
For the description of this option, see Set Unconditional Code Breakpoint on
page 4-7 under the B command.
Considerations
When debugging accelerated programs, you can set breakpoints in TNS code only on
instructions that are register-exact or memory-exact points. These points are marked in
displays by the I and PMAP commands. For more information, see Rules About RISC
Breakpoints on page 2-7.
Examples
106,04,00192-b 5 + 3, (d; t; r)
106,04,00192-b uc.2, 100+2, (d;t;r)
248,04,00092-B N 0X7002D058, (D;T;R)
Display Breakpoints
The B command can display currently set breakpoints for the process being debugged.
In addition, as each breakpoint is set, Debug displays information describing
that breakpoint.
The display breakpoints form of the B command is:
B [ * ]
Considerations
For more information on how Debug displays the breakpoint information, see the
display formats described on the following pages.
* displays RISC breakpoints set as a result of setting TNS breakpoints in an
accelerated program. Without the asterisk (*), only breakpoints explicitly set in a
B or BM command are displayed.