TACL Reference Manual

UTILS:TACL Commands and Functions
HP NonStop TACL Reference Manual—429513-018
8-49
DEBUG Command
read access to the program file. (For a description of process accessor IDs, see
the Guardian User’s Guide.)
•
A group manager can debug any process whose process accessor ID matches the
user ID of any user in the group. The manager must also have read access to the
program file.
•
The super ID can debug any process. Only the super ID can debug privileged
processes.
•
The process you name in the DEBUG command does not enter the debug mode
until it executes its next instruction in the user code space. The process cannot
enter the debug state while executing system code.
•
DEBUG is the default debugger. When you enter the DEBUG command, DEBUG
is invoked unless INSPECT was designated as the debugger for the process when
the process was created. You can designate INSPECT as the default debugger in
any of these ways:
°
Issue a SET INSPECT ON command, and then run the program.
°
Use the INSPECT option with the RUN command.
°
When compiling a source program, or when using BINDER, include a compiler
directive that specifies that the debugger for the program is to be INSPECT.
H-Series Usage
The program DEBUG is not available for use on systems running H-series software.
The DEBUG command invokes a debugger, it can be Inspect, Native Inspect
(eInspect, which is not in the family of Inspect debuggers), or Visual Inspect.
The rules about which debugger gets invoked are approximately the same as for the
RUND command. That is, if the INSPECT attribute is set ON anywhere (in the object
file during compilation, or on the TACL command line using the SET command), you
will get a debugger in the Inspect family (either Inspect or VI), unless of course neither
of these debuggers is available, and then you get the default debugger, eInspect. If
the Inspect attribute is OFF, you get Native Inspect (eInspect).
Inspect is invoked only for TNS accelerated/interpreted programs (never for TNS/E
native programs), while Visual Inspect can handle both of these. Native Inspect
handles only TNS/E native programs and snapshots.
Examples
•
To debug a running process named $ERRER, enter:
14> DEBUG $ERRER
DEBUG or INSPECT then prompts for commands.