Inspect Manual

Error and Warning Messages
Inspect Manual—429164-006
A-41
359
Inspect cannot predict when a modify operation may have no effect. Chances are
highest when you are modifying a variable that has been used recently or is about to
be used.
359
This warning is reported for accelerated programs when Inspect reports a debugging
event and the current location is not a memory-exact point. In this case, some values
in memory may be out of date, because more recent values are stored in registers.
This is most likely to be the case for variables to which values have been recently
stored.
Most commonly, programs are left at non-exact points as a result of data access
breakpoints. Issuing a STEP command will advance the program to the next memory-
exact point, at which displayed memory will be consistent.
360
The DMON process reported an internal error. You should record any information that
is reported and contact your Tandem representative. Such an error will prevent you
from performing the operation that you attempted; however, other operations should
still work.
361
This error is reported if you attempt an operation that only applies to an accelerated
program when you are debugging a program that has not been accelerated or is not
executing on a TNS/R system.
362
The version of the accelerator used to create the object file is a version that is not
recognized by Inspect. You may need to use a newer version of Inspect.
Current location is not a memory-exact point;
displayed values may be out of date;
the location reported is an approximate TNS location
DMON internal error: number
Contact your Tandem representative
Operation available only on an accelerated program
Object file was created by an unrecognized Accelerator
version; file: file-name