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-32
C Command
Examples
100,01,00011-BM L+2, R, (D; T; R)
100,01,00011-BM UC.2, 400, W, (D;T;R)
100,01,00011-BM SC.0, 2342, W, (D;T;R)
248,02,00067-BM 0x4FFFFEFC, R, (D;T;R)
C Command
The C command clears one or all code breakpoints (unconditional, conditional, trace,
and execute). The form of the C command is:
address
is the code address of the breakpoint to be cleared. For more information, see
Address Syntax on page 3-12. Any address mode used to set a code breakpoint
may be used to clear one. Any code breakpoint can be cleared without privilege,
even if privilege was required to set it.
Address value 0 clears all code breakpoints for the current process but does not
affect breakpoints set with the ALL option; privilege is not required.
Address value -1 clears all code breakpoints set in this processor, including those
set in and for other processes and those set with the ALL option; this value is valid
only if you are debugging in privileged mode.
If you omit address, Debug clears the current breakpoint.
Examples
106,01,00012-C 527+215 ! Clears the breakpoint at %000744.
106,01,00012-C UC.2,325 ! Clears breakpoint in user code segment 2.
106,01,00012-C0 ! Clears all breakpoints in the current process.
106,01,00012-C -1 ! Clears all breakpoints in the processor.
248,02,00012-C 0x7045FEF0 ! Clears the breakpoint in RISC code.
C [ address ]
[ * | 0 ]
[ -1 ]
* clears all breakpoints for the current process; this is equivalent to specifying
the address value 0.