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-51
Privileged Commands
commands). If we want to look at information in another PIN's PCB, or our own, we
can use the PCB option on the D command.
In this example, we are looking at the PCB for PIN 265, starting at byte offset 8 for two
16-bit words. Byte 8 has the starting priority, and byte 9 has the current priority. Bytes
10 and 11 make up a 16-bit word that contains the PIN. Note that the PIN matches the
one we entered.
We have the example program running as PIN 265 in the same processor. The
program has a breakpoint at the end of the EXAMPLE_FILL_ARRAY procedure. First,
we look at the breakpoint table.
With the privileged mode enabled, we can see breakpoints to all the processes. Thus,
while running PIN 10, we also see PIN 265's breakpoint.
V Command
We can use the V command to view and manipulate information for another PIN. In
this example, we vector to PIN 265. We use the ? command to see the environment
before and after the V command has been entered.
050,03,00010-D PCB #265 + #8, 2 :h
80C26F28: 0xA8A8 0x0109
050,03,00010-= %ha8
= %000250 #00168 0x00A8 '..'
050,03,00010-= 0x0109
= %000411 #00265 0x0109 '..'
050,03,00010-B
N: 0x70000568 INS: 0x03E00008 PIN: #00265
INS: JR ra
050,03,00010-?
BASE SEGMENTS: SYSTEM DATA = %000001
SYSTEM CODE = %000005
SYSTEM LIB = %020400
USER DATA = %020754
USER CODE = %020736
V PIN = 012 (#010)
USE SEGMENT ID = %002000
BASE STANDARD IN
BASE STANDARD OUT
TERM \M5.$ZTN00.#PTYX5AA
PRV = ON
050,03,00010-V #265