CRE Programmer's Guide

CRE Services
Common Run-Time Environment (CRE) Programmer’s Guide—528146-004
2-64
Locating the Corrupter of TNS CRE Pointers
Considerations for Using Visual Inspect
If you are using Visual Inspect with the CRE, note the following considerations:
•
Visual Inspect can find a global variable of any language independent of the
language of the scope in the Program Control View. To find a global identifier, open
a Display dialog and then select the Global radio button. Type your variable or
expression in the Expression box and click OK.
First Visual Inspect looks in the globals associated with the language of the current
scope. Next, Visual Inspect looks in the other globals space.
°
If you are debugging a mixed C and TAL program that has the same named
global defined in C and TAL, and if the current execution point is in C, Visual
Inspect finds the C global.
°
If the current execution point is in TAL, Visual Inspect finds the TAL global.
°
If the global exists in only one language, and other language is the current
scope, Visual Inspect finds the one global that exists.
•
Visual Inspect can find the correct identifier in the case of an ambiguity.
°
If your program contains both a C and a TAL variable named VAR_A, Visual
Inspect finds the TAL identifier if the language of the source in the current
window is TAL.
°
If the source of the current window is C, and you want to find the TAL identifier,
you should either use the Display dialog and specify the scope you want, or
open a scope view of any TAL routine and create a watch item from that
window.
•
Because the CRE provides multiple connections to a single open of an operating
system file, the Visual Inspect Opens Manager shows only one open for each
standard file, regardless of how many connections the CRE has granted for the
file. If none of your routines have the standard file open, the file does not appear in
the file list displayed by Visual Inspect.
•
You cannot mix identifiers from different languages within an expression in the
Visual Inspect Expression box.
Locating the Corrupter of TNS CRE Pointers
If the TNS CRE reports error 13, “MCB pointer corrupt,” you can use the Inspect or
Visual Inspect debugger to help locate the statement that is overwriting the MCB
pointer.
Using Inspect
By using low-level Inspect commands, you can set a memory breakpoint at location
G[0]. If your program writes data at the memory location at which you have set a