Inspect Manual

Using Inspect With Accelerated Programs on TNS/R
Systems
Inspect Manual—429164-006
16-8
Using Inspect to Debug Accelerated Programs
1 Code breakpoints can only be set on locations that are memory-exact points.
2 Data might still be in registers; therefore, displayed memory might be out of date.
3 Memory values might be preloaded in registers so modification might have not effect.
4 Register information might be out of date. i.
Using Inspect to Debug Accelerated Programs
The following subsections provide useful information for using Inspect to debug
accelerated programs. Section 6, High-Level Inspect Commands provides complete
syntax and detailed explanations of all commands discussed in this section.
Program Libraries
It is possible to call an accelerated user library from a program that has not been
accelerated. Similarly, it is possible to call a user library that has not been accelerated
from a program that has been accelerated.
When debugging such programs, the constraints and functionality that apply to
debugging accelerated programs apply to the accelerated portion of the program, but
not to the portion that has not been accelerated. i
Code Breakpoints
When debugging a TNS program, you can set code breakpoints at any location in the
program. When debugging accelerated programs, however, Inspect only allows TNS
code breakpoints to be set at locations that are memory-exact points.
If you attempt to set a TNS code breakpoint at a location that is not a memory-exact
point, the following error message is issued:
.
** Inspect error 197 ** Location deleted by optimizations
Modify
variables
Yes Yes Yes
3
Yes
3
Display
TNS
registers
Yes Yes Yes
4
Yes
4
Modify TNS
registers
Yes Yes No No
Table 16-1. Debugging Capabilities in Accelerated Programs on TNS/R
Systems (page2of2)
Action
TNS
Program
Accelerated
Program at a
Register-
Exact Point
Accelerated
Program at a
Memory-
Exact Point
Accelerated
Program at a
Non-Exact
Point