Guardian Programmer's Guide

Debugging, Trap Handling, and Signal Handling
Guardian Programmer’s Guide — 421922-014
25 - 7
Specifying the Debugging Environment
Switching Debuggers During a Debugging Session
The native debuggers Inspect, Visual Inspect, and Native Inspect (in the TNS/E
environment only), allow you to switch from one debugger to an other while debugging
a process. The ability to switch debuggers is especially useful if a process enters the
debug state under control of an inappropriate debugger; for example, if a TNS program
automatically enters the debug state under control of Native Inspect. Since Native
Inspect does not support TNS mode debugging, you could use this feature to switch to
Inspect. See the Inspect Manual, the Native Inspect Manual, and the Visual Inspect
online help for details.
Using Compiler Directives
If you specify the INSPECT compiler directive in your TAL or pTAL program, then the
process automatically runs under the Inspect program whenever the process enters
the Debug state.
The SAVEABEND compiler directive in your TAL or pTAL program also implies that the
Inspect program is the debugger, as well as specifies a saveabend file for the process.
See the TACL Reference Manual for details on these compiler directives.
Some other programming languages offer equivalent capabilities. Refer to the
appropriate programming language manuals.
Using the Binder and nld or eld Utilities
The Binder and the nld utility (in the TNS/R environment) and the eld utility (in the
TNS/E environment) also have commands that allow you to select the Inspect program
(in the TNS/R environment) or the Native Inspect program (in the TNS/E environment)
while linking. The SET INSPECT ON command, in either utility, causes your process
to automatically run under the Inspect program on TNS/R systems. On TNS/E
systems, SET INSPECT ON sets Visual Inspect as the default debugger.
The SET SAVEABEND ON command also implies the Inspect program and specifies a
saveabend file for the process.
See the Binder Manual for details on these Binder commands. See the nld Manual for
information about using the nld utility in the TNS/R environment. See the eld Manual
for information about using the eld utility in the TNS/E environment.
Using the TACL SET INSPECT Command
You can use the TACL SET INSPECT command to establish the debugging
environment for processes that will be started by the current TACL process. The
following example establishes the Inspect program as the default debugger:
> SET INSPECT ON