Inspect Manual

Using Inspect on a TNS/E System
Inspect Manual—429164-006
18-8
Using Inspect to Debug TNS Programs on TNS/E
Systems
Using Inspect to Debug TNS Programs on
TNS/E Systems
Debugging TNS programs on TNS/E systems is virtually the same as debugging TNS
programs on TNS/R systems. The capabilities of Inspect are the same on the two
platforms, except that a few Inspect commands have the limitations listed in
Table 18-2.
Much of the information in Section 16, Using Inspect With Accelerated Programs on
TNS/R Systems also applies to debugging TNS programs on TNS/E systems, with the
exceptions noted in Table 18-2.
In general, descriptions throughout this manual that pertain to debugging accelerated
programs on TNS/R systems also apply to debugging TNS programs on TNS/E
systems.
Table 18-2. Considerations for Inspect Commands on TNS/E Systems
Command Limitation on TNS/E Systems
ADD PROGRAM
You cannot add a TNS/E process or a TNS/E snapshot to
an Inspect debugging session on a TNS/E system.
DISPLAY
REGISTER BOTH TNS/E registers cannot be viewed using Inspect.
Inspect displays only the TNS registers on TNS/E systems.
ICODE
ICODE BOTH
The ICODE output for an OCA process will show safe-point
annotations, but the ICODE output for a snapshot of an
OCA process will not show safe-point annotations. There is
no display of TNS/E ICODE.
Inspect does not display Itanium processor instruction
codes.
INFO OBJECTFILE
Inspect does not read TNS/E native object files.
INFO SAVEFILE
Inspect does not read TNS/E snapshot files.
SOURCE
Shows register-exact point and deleted statement
annotations for an OCA process but not for an OCA
snapshot.
TRACE
Does not show any information about TNS/E native frames.