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
Sample Debug Sessions
Debug Manual—421921-003
F-49
Privileged Commands
Privileged Commands
Certain commands and addresses are restricted unless PRV has been turned ON.
This is allowed only when the user is the super ID (255, 255). In order to run the
following commands, you need to be the super ID. Use Debug commands on another
program running in the same processor. The environment to run Debug can be
chosen arbitrarily. For our example program, we used the File Utility Program (FUP). If
you are debugging in Inspect, enter the command SELECT DEBUGGER DEBUG to
access Debug.
Using G-address Mode to Access Data
The G-address mode allows access to data in the system’s global area. Attempting to
use the G-address mode when you are not a privileged user results in an error.
$DATA06 CRGTT 9> fup /cpu 3, debug/
INSPECT - Symbolic Debugger - T9673D40 - (30SEP97) System \M5
Copyright Tandem Computers Incorporated 1983, 1985-1997
INSPECT
050,03,00010 FUP #FUP^MAIN + %0I _FUP_select debugger debug
DEBUG P=%120301, E=%000207, UC.%00
050,03,00010-D G 123I, T#8*#12 :h
** DEBUG error 7: PRV ON is required to perform command.
050,03,00010-?
USE SEGMENT ID = %002000
BASE STANDARD IN
BASE STANDARD OUT
TERM \M5.$ZTN00.#PTYX5AA
PRV = OFF
050,03,00010-PRV ON
050,03,00010-?
BASE SEGMENTS: SYSTEM DATA = %000001
SYSTEM CODE = %000005
SYSTEM LIB = %020400
USER DATA = %020754
USER CODE = %020736
V PIN = 012 (#010)