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-3
Execution Options
Execution Options
Three modes of execution are possible on a TNS/R system: TNS mode, accelerated
mode, and native mode.
Much of the code in software products supplied by HP for TNS/R systems has been
produced by TNS/R native compilers. Users can also use native compilers to produce
their own native TNS/R code. For more information, see the C/C++ Programmer's
Guide and the pTAL Programmer’s Guide. Native code consists of RISC instructions
that have been optimized to fully exploit the RISC architecture. Program files
containing such code are called native program files.
Programs produced by compilers that are not TNS/R native compilers also execute on
TNS/R systems. Such programs contain TNS object code. Program files containing
TNS object code are called TNS program files.
For most TNS program files, you can significantly improve performance by processing
them with the Accelerator to make use of performance features of the RISC instruction
set.
The Accelerator processes a standard TNS object file and augments that file by adding
the equivalent RISC instructions. TNS object files that have been optimized by the
Accelerator are called accelerated object files, or accelerated program files if they
include a main procedure.
Running accelerated program files can significantly improve performance over simply
running TNS program files directly on the TNS/R processor. The Accelerator, however,
provides optimization options that can affect debugging the program.
The following paragraphs provide an overview of execution options and describe how
two Accelerator options affect debugging. For more information on using the
Accelerator, see the Accelerator Manual.
Running Native Program Files
Debugging a native program is similar to debugging the RISC portions of an
accelerated program, but you should be aware of a few differences.
•
Most addresses in native mode must be expressed in 32-bit address form. For
example, to set a breakpoint in native code, you must use the 32-bit address form
to specify the breakpoint address:
248,01,012-B 0x70451210
•
Because of differences in stack layout and contents between native mode and
TNS or accelerated mode, the method of specifying a particular stack frame to
begin a stack trace differs. For more information on displaying a stack trace, see
the description of the T Command on page 4-68.