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 Manual—421921-003
xiii
About This Manual
This manual describes the features and use of the Guardian debug facility, Debug.
This version of Debug runs on HP NonStop Series/RISC (TNS/R) processors. TNS/R
processors are based on reduced instruction-set computing (RISC) technology.
This version of the HP NonStop operating system also supports execution of programs
written for the HP NonStop Series (TNS) processor environment, although TNS
processors are no longer supported. TNS processors were based on complex
instruction-set computing (CISC) technology.
Who Should Use This Manual
Debug is a low-level debugging tool. It is intended to be used by system and
application programmers.
To use this product, you must be familiar with the Transaction Application Language
(TAL) or another programming language, such as pTAL, C, C++, COBOL, or Pascal.
You must also be familiar with system hardware registers and addressing modes.
A high-level symbolic debugger, the Inspect product, is also provided by HP. Many
people find it more convenient to use a symbolic debugger than a low-level debugger,
because a symbolic debugger allows you to use the names of the symbols in your
program rather than the addresses and registers that the compiler assigned. You might
consider using the Inspect debugger if it is possible to do so. Using the Inspect
debugger, however, requires that the Inspect monitor process (IMON) be running on
the node. If you prefer a symbolic debugger, refer to the Inspect Manual.
Debug is a part of the operating system and is always available. Debug is required for
debugging address spaces that the Inspect debugger cannot debug, such as:
•
Monitor process
•
Memory manager
•
$SYSTEM disk process