Inspect Manual

Inspect Concepts

Inspect Manual—429164-006

2-2

Starting an Inspect Session

There are four ways to start an Inspect session:



Run Inspect directly.



From the TACL prompt, enter:

>RUN INSPECT

or:

>INSPECT



From the OSS shell, enter:

gtacl -p inspect



Run your program with the debug option.



From the TACL prompt, enter:

>RUND program



From the OSS shell, enter:

run -debug -inspect=on program



Issue a debug request on a running program.



A debug event occurs in a program that has your terminal specified as its home

terminal or debugging terminal. For more information, see Debug Events on

page 2-8.

The first of these events always starts a new Inspect session. The second, third and

forth start a new Inspect session if your terminal does not already have an Inspect

session.

The first two options have been enhanced to support the OSS shell. In all cases,

Inspect will be started as a Guardian process.

To avoid incompatibilities between Guardian and the OSS terminal I/O when

debugging an OSS process, change Inspect’s command terminal to an existing

Guardian terminal using the TERM command as soon as Inspect comes up.

At the start of an Inspect session, the Inspect process displays a banner similar to this:

This banner signifies the start of the session (\sysname is the system on which the

Inspect process is running).

After printing the banner, the Inspect process looks for an EDIT file named INSPLOCL

in the volume and subvolume containing the Inspect program file. If this INSPLOCL

file exists, Inspect reads and executes the Inspect commands it contains.

INSPECT - Symbolic Debugger - T9673D40 - (29JUL03) System \sysname