Native Inspect Manual (H06.07+)

Introducing Native Inspect

Native Inspect Manual—528122-006

1-12

Debugger Selection Criteria

Explicitly Starting Native Inspect

At the TACL prompt, enter a RUN command specifying the Native Inspect object file

(EINSPECT) and the CPU in which the process is running (the process that you want

to debug).

For example, to start Native Inspect in CPU 2 in the Guardian environment, enter:

To start Native Inspect in CPU 2 in the OSS environment, enter:

After Native Inspect initializes, you must enter the attach command so that you can

examine a TNS/E native process. The process must be running under your user ID (or

you must be either the super ID or the group manager of the user), and must be

running in the same CPU as the instance of Native Inspect you started.

To examine a snapshot file after starting Native Inspect, use the snapshot command.

For more information about starting Native Inspect and about accessing source and

loading symbols, in addition to an extended example of a Native Inspect session, see

Section 2, Using Native Inspect

\SYSTEM.$D0117.INSPECT 1> einspect / cpu 2 /

TNS/E Native Inspect gdb Debugger [T1237 - 13-Jan-2005 12:45]

Native Inspect (based on GDB) is covered by the GNU General Public

License.

Type "show copying" for conditions for changing and/or distributing

copies.

Type "show warranty" for warranty/support information.

Working directory \PIPPIN.$D0117.TESTS.

SUPPORT: http://egarth.cac.cpqcorp.net

(eInspect 2,-2):

/G/SYSTEM/SYSTEM gtacl -cpu 2 -p einspect

TNS/E Native Inspect gdb Debugger [T1237 - 04-Apr-2006 09:00]