Inspect Manual

Inspect Manual—429164-006
16-1
16
Using Inspect With Accelerated
Programs on TNS/R Systems

Accelerated Program Debugging Overview

Assumptions on page 16-2

Variances on page 16-2

Performance and Debugging of Accelerated Programs on page 16-3

Accelerated Program Transitions on page 16-3

Accelerated Program Debugging Concepts on page 16-4

Debugging Boundaries on page 16-5

Accelerator Debugging Options on page 16-6

Using Inspect to Debug Accelerated Programs on page 16-8

Program Libraries on page 16-8

Code Breakpoints on page 16-8

Data Breakpoints on page 16-9

Event Reporting on page 16-14

Data Access Limitations on page 16-15

TNS Register Access Limitations on page 16-16

Commands Useful When Debugging Accelerated Programs on page 16-17
Accelerated Program Debugging Overview
TNS programs, compiled on TNS/R systems by TNS compilers rather than TNS/R
native compilers, also execute on TNS/R systems. TNS programs can be accelerated
to run more efficiently on TNS/R systems.
Inspect supports the debugging of both accelerated and non-accelerated TNS
programs on HP NonStop TNS/R systems. Debugging non-accelerated programs on a
TNS/R system is nearly identical to debugging them on a TNS system. The only
difference is in the area of data breakpoints, which might be reported at slightly
different locations than on a TNS system. On a TNS/R system, you can debug non-
accelerated TNS programs both at the source level and at the TNS system level.
Accelerating a TNS program yields improved program performance, but can make the
program more difficult to debug. When debugging an accelerated program on a
TNS/R system, synchronization points—points at which there is a direct