Inspect Manual

Inspect Manual—429164-006
17-1
17
Using Inspect With TNS/R Native
Programs

TNS/R Native Overview

TNS/R Native Program Debugging Concepts on page 17-1

TNS/R Native Compilers and Linkers on page 17-2

Optimization Levels on page 17-3

Using Inspect to Debug TNS/R Native Programs on page 17-4

SRLs on page 17-4

Dynamic-Link Libraries (DLLs) on page 17-5

Code Breakpoints on page 17-6

Signals on page 17-6

Commands Useful When Debugging Native Programs on page 17-6

Debugging at the TNS/R Native Machine Level on page 17-12

Examples on page 17-13
TNS/R Native Overview
Three modes of execution are possible on a TNS/R system: TNS/R native mode, TNS
mode, and accelerated mode.
Much of the code in HP-supplied software products for TNS/R systems has been
produced by TNS/R native compilers. Users can also use TNS/R native compilers to
produce their own native TNS/R code. (Refer to the C/C++ Programmer’s Guide and
the pTAL Reference Manual.) TNS/R native code consists of RISC instructions that
have been optimized to capitalize on the RISC architecture. Program files containing
such code are called native program files.
TNS programs, produced by TNS compilers executing on TNS/R systems, also can
execute on TNS/R systems. TNS programs contain TNS object code, and program
files containing TNS object code are called TNS program files.
TNS/R Native Program Debugging Concepts
TNS/R native programs run faster than accelerated or TNS programs, in part because
the native code is optimized. The optimization level option used when compiling
TNS/R native programs directly affects source-level debugging. (Most source-level
debugging capabilities are preserved. Source-level debugging restrictions include