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-30
Set Trace Memory-Access Breakpoint
Considerations
•
Change access is not allowed with trace memory-access breakpoint.
•
Debug displays this header each time the breakpoint location is accessed in the
specified manner:
°
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 code segment. An r in the
space-identifier, in place of the segment index, indicates native code;
that is, SCr, SLr, and so forth. (UC appearing without a segment index is
equivalent to UCr.)
°
RISC mode
TRACE $PC=code-address
In native mode, code-address is a 32-bit hexadecimal value.
•
For infromation about setting an unconditional memory-access breakpoint, see
Considerations on page 4-25.
Examples
106,01,00012-BM L2, W, (2.1000)<<1 ? #16
106,01,00012-BM UC.2, 524, W, L+3 ? 6
106,01,00012-BM C 200, R, R0 ? 10
106,01,00012-BM 0x00080030, w, $a1 ? 2
For more example for strace memory-access breakpoint, see Appendix F, Sample
Debug Sessions.