10.0;dq (debug_quit) *DM*, revision 1.0, 88/03/22
dq (debug_quit) generate a quit fault in a process
usage: dq [entry_name [-c | -s | -b | -i]]
DESCRIPTION
The dq command generates a quit fault, which normally interrupts
execution of the current program and returns the process to the calling
program. This command affects the process associated with the window
that contains the cursor.
ARGUMENTS
entry_name (optional)
Specify the name of the window or window group whose
process is to receive the fault. Note that this is valid
only for processes with windows. To stop background
processes, use the shell command sigp (signal_process).
If the name of the window or group appears as a text
string somewhere on the display, you may use the
following time-saving feature: place the cursor on the
name, then press <MARK>. Now issue the dq command. dq
uses the marked name for the entry_name argument.
Default if omitted: send fault to the process whose
window is under the cursor
OPTIONS
If you do not specify an option dq generates a normal quit fault and
halts whatever program is currently running.
-c FFFFFFFF Generate an arbitrary asynchronous fault with the
specified hexadecimal status (FFFFFFFF).
-s Stop the entire process in a controlled way, if
possible. Close open streams, files, and pads. The
shell's parent process is stopped and closed, too.
-b Blast process; do not execute further user-mode
instructions. Open streams, files, and pads are not
closed. If you blast processes, you should shut your
node down and reboot.
-i Generate an interrupt fault. Open streams, files, and
pads are not affected. This is equivalent to a SIGINT
(interrupt) fault in UNIX.
SEE ALSO
More information is available. Type the following at an Aegis shell
prompt:
help ds For details about suspending a process
help dc For details about restarting a suspended process
help eef For details about stopping a shell and its process