HP 3000 Manuals HP 3000 Manuals
HPSETDUMP (NM)
(new)
The HPSETDUMP intrinsic arms the system debugger call from a process
abort. If a process aborts, HPSETDUMP enables automatic execution of a
set of system debugger commands. The process can be the current process
or any child of the current process created after the intrinsic call.
That is, the intrinsic affects all new child processes and all
generations thereafter.
Before a process aborts, the debugger is called to execute the commands
you entered in the cmdstr parameter. The commands are contained in a
character array of up to 255 characters, left-justified, with a
delimiting character as the first and last character of the command
string. Commands that attempts to obtain user input cause an error when
executed by the debugger.
If the process that aborts is being run from a job, the process will
terminate after executing the command string.
If the process is being run from a session the specified command string
is executed first. Next, the debugger stops to accept interactive
commands with I/O performed at the user terminal if the following
conditions are met:
* The abort did not occur while in system code.
* The process entered the abort code via a native mode interrupt
(typically caused by arithmetic and code-related traps).
Once the debugger accepts interactive input, the user is free to enter
any DEBUG command. The user may choose to resume the process or have it
terminate with the CONTINUE command.
If the cause of the abort is a stack overflow, a stack trace is printed
and the process is terminated immediately thereafter. The command string
is not executed.
The status parameter, a 32-bit signed integer passed by reference is
optional, but recommended. It indicates status in two fields. One
reports the presence of errors and warnings, and the other indicates the
subsystem where they occurred. If an error or warning condition is
encountered, and you did not specify the status parameter, HPSETDUMP
causes the calling process to abort. Using the status parameter in MPE
XL is analogous to using condition codes in MPE V/E.