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

Error Messages
Debug Manual—421921-003
A-25
100
100
Cause. The command referenced a floating-point register, but either the PIN does not
use IEEE floating-point instructions or an IEEE floating-point instruction is not executed
at this point in the program.
Effect. The command is not executed.
Recovery. If you think the program at this PIN uses IEEE floating-point instructions,
you might need to delay the command until an IEEE floating-point instruction is
executed and the IEEE floating-point usage flag is enabled in the program control
block (PCB).
101
Cause. An IEEE floating-point register was referenced in the specified command
syntax. Unlike the general purpose registers $00 through $31, IEEE floating-point
register values cannot be used in the syntax of some commands, because Debug can
handle only 32-bit integer expressions and it cannot determine if the specified IEEE
floating-point register is used as a 32-bit integer.
Effect. The command is not executed.
Recovery. If you need the contents of the IEEE floating-point registers, first display
the value of the register and then use this value with the command syntax. Note that
the register value must be an integer that can be expressed in 32-bit form.
102
Cause. The command tried to set a Memory Access Breakpoint at a location where a
code breakpoint either exists in same process or in all processes in same processor.
Effect. The command is not executed.
Recovery. Try the command after removing the existing code breakpoint at the same
location.
PIN does not use IEEE floating point.
IEEE floating-point registers cannot be used here.
Cannot set the Memory Access Breakpoint at this address as a code breakpoint
already exists at given location.