Inspect Manual

Using Inspect With Accelerated Programs on TNS/R
Systems
Inspect Manual—429164-006
16-15
Data Access Limitations
There are some debugging events that may be reported when the current location is a
non-exact (not a memory-exact) point: i

A data breakpoint.

A process entry into Inspect.

A run-time trap.

An INSPECT HOLD command issued to suspend a running process.

A TNS/R code breakpoint. (TNS/R code breakpoints may only be set in Debug.)
When a debugging event occurs, Inspect determines the consistency of the program
state at the current program location. The current location can be one of the following:

Register-exact point
Inspect presents you with the most information about the TNS view of the current
program state at register-exact points. At a register-exact point, TNS registers and
memory are consistent.

Memory-exact point
Inspect presents you with less up to date information at memory-exact points. At a
memory-exact point, displayed memory is accurate and some TNS register values
may be out of date.i

Non-exact point
Inspect presents you with the least accurate information at non-exact points. The
reported current program location is only approximate. Displayed memory may be
out of date, memory modifications may have no effect, and TNS registers are out
of date.
If your current program location is a non-exact point, Inspect will issue the following
warning when a debugging event is reported:
Data Access Limitations
The following paragraphs describe data access limitations that exist at various points in
your program.
At Register-Exact Points
When the current program location is a register-exact point, all memory has been
updated and no data is loaded into TNS/R registers. You can display and modify
variables without concern that memory is out of date.
** Inspect warning 359 ** Current location is not a memory-exact
point;displayed values may be out of date; the location reported is an
approximate TNS location