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

Using Debug on TNS/R Processors
Debug Manual—421921-003
2-15
TNS and TNS/R Register Correspondence
The bits and the decoding for the $FCR31 register are as follows:
Bit Meaning
<7> FS: 0 or 1 When the FS bit is set, denormalized results are flushed to 0.
<8> C: 0 or 1 The C bit is set to 1 if the condition is true, and the bit is cleared to
0 if the condition is false.
<14:19>: CAUSE The CAUSE bits reflect the results of the most recently executed
instruction. They identify the exceptions raised by the last
floating-point operation and raise an interrupt or exception if the
corresponding ENABLE bit is set. If more than one exception
occurs on a single instruction, each appropriate bit is set. Note that
the CAUSE bits are managed by the NonStop operating system,
the user code has no access to them.
<20:24>: ENABLE A floating-point exception is generated any time a CAUSE bit and
the corresponding ENABLE bit are set. A floating-point operation
that sets an enabled CAUSE bit forces an immediate exception.
<25:29>: FLAGS The FLAG bits are cumulative and indicate that an exception was
raised by an operation that was executed after the FLAG bits were
explicitly reset. The FLAG bits are set to 1 if an IEEE 754
exception is raised; otherwise, they remain unchanged. A bit in the
FLAG field is set only if the corresponding exception condition
occurs and the corresponding trap is disabled.
<30:31>: Round Mode These bits specify the rounding mode that the floating-point unit
(FPU) uses for all floating-point operations.