CRE Programmer's Guide

CRE Services
Common Run-Time Environment (CRE) Programmer’s Guide—528146-004
2-63
Selecting a Debugger
Selecting a Debugger
You can use the Inspect, Native Inspect, or Visual Inspect symbolic debugger to debug
a program that uses the CRE.
•
To specify Inspect or Native Inspect as the debugger, run your program using the
RUND TACL command; for example:
RUND mtro ...
•
To specify Visual Inspect as the debugger, use the RUNV TACL command, as
follows:
RUNV mtro ...
When you run your program using the RUND or RUNV TACL command, your
program enters the appropriate debugger before it executes any of your program’s
instructions.
Considerations for Using Inspect or Native Inspect
If you are using Inspect with the CRE, note the following considerations:
•
Because the CRE provides multiple connections to a single open of an operating
system file, an Inspect INFO OPENS command 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 Inspect.
•
When you use the Inspect debugger to display your program’s identifiers, it
attempts to locate the identifier you specify, regardless of the language of the
routine you are currently inspecting. For example, if you are inspecting a C routine,
you can display the TAL variables VAR_A and VAR^B by entering:
display var_a, var^b
The Inspect debugger locates identifiers whose names you specify in a display
command unless it cannot resolve an ambiguity. For example, if your program
contains a C and a TAL variable named VAR_A and the language of the current
scope is C, Inspect finds the C variable when you enter:
display var_a
If you want to display the TAL identifier, you must use the SET LANGUAGE
command as follows:
SET LANGUAGE TAL
display var_a
•
You cannot mix identifiers from different languages within an expression in an
Inspect display command.