Native Inspect Manual (H06.13+, J06.03+)

Figure 3 Debugger Selection for a TNS Process Running on TNS/E

If you are using Native Inspect and the current process is a TNS process on a TNS/E system, the

capabilities available to you are described in Debugging TNS Processes (page 27).

Explicitly Starting Native Inspect

At the TACL prompt, invoke the Native Inspect object file (EINSPECT) explicitly, using the RUN

command, or implicitly, by entering the filename alone. Use the CPU option to select the CPU in

which the process you wish to debug is running.

For example, use the following procedure to start Native Inspect in CPU 2 in the Guardian

environment:

1. At the TACL prompt, invoke EINSPECT, as follows:

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

2. The Native Inspect start up screen is displayed as follows:

TNS/E eInspect gdb Debugger [T1237 - 20-Dec-2011 16:43]

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 \PELICAN.$SYSTEM.STARTUP.

(eInspect 2,-2):

3. Enter debugger commands at the following system prompt:

(eInspect 2,-2): help

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

22 Introducing Native Inspect