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-7
B Command
B Command
The B command sets code breakpoints and displays code and memory-access
breakpoints. The B command has five functions:
•
Set Unconditional Code Breakpoint on page 4-7
•
Set Conditional Code Breakpoint on page 4-11
•
Set Trace Code Breakpoint on page 4-13
•
Set Execute Code Breakpoint on page 4-15
•
Display Breakpoints on page 4-16
Each function is defined by a unique syntax. Each function and its syntax is described
in the following pages.
Set Unconditional Code Breakpoint
The B command can set an unconditional code breakpoint. An unconditional code
breakpoint causes the process to enter the debug state each time the breakpoint
location is executed. The unconditional form of the B command is:
address
is the code address where the breakpoint is to occur. For more information, see
Address Syntax on page 3-12. The address mode must follow these guidelines:
•
Use UC, UL, SC, SL, and C address modes for TNS code.
•
Use 32-bit extended address or N address mode for native or accelerated
code.
•
You must be privileged to set a breakpoint in protected code areas, which
include:
°
All system code: SC, SL, SCr, SLr
°
Code anywhere in a UC, UL, UCr, or SRL space that contains PRIV or
CALLABLE procedures
•
To set a breakpoint in a UC, UL or SRL space, you must have read access to
the object file for that library.
B address [, ALL ]