TACL Reference Manual

UTILS:TACL Commands and Functions

HP NonStop TACL Reference Manual—429513-018

8-48

DEBUG Command

Use the DEBUG command to initiate debugging for a process that is already running.

Entering the DEBUG command is one way to invoke the Debug program or the Inspect

debugger.

If you do not specify a process ($process-name or cpu,pin), the Debug and Inspect

programs begin debugging the process most recently started by TACL, if that process

is still in existence.

For information on the Debug program, see the Debug Manual. For information about

the Inspect symbolic debugger, see the Inspect Manual.

The program DEBUG is not available for use on systems running H-series software.

See the Considerations section on page 8-49 for more details.

\node-name

is the system where the process resides.

$process-name

is the name of the process or process pair.

cpu,pin

is the CPU number and process number for the process.

TERM [\node-name.]$terminal-name

is the new home terminal of the process being debugged. To enter DEBUG or

INSPECT commands from a terminal other than the current home terminal of the

process being debugged, you must designate that terminal as the new home

terminal with the TERM option. You must include the node-name if the new home

terminal is connected to a system other than the current default system.

If you omit the TERM option, DEBUG or INSPECT prompts appear on the original

home terminal of the process.

Considerations

•

You can enter the DEBUG command interactively only, not in an input file or an

OBEY file.

•

Unless you are a group manager or the super ID, you can debug only those

processes with process accessor IDs that match your user ID. You must also have

DEBUG [ [\node-name.]{$process-name | cpu,pin } ]

[ , TERM [\node-name.]$terminal-name ]