Guardian Procedure Calls Reference Manual

error
output
INT:ref:1
returns a file-system error number indicating the outcome of the process debug attempt. Possible
values include these:
No error.0
The specified process does not exist.11
Invalid name. This error can occur when the supplied process ID is improperly formed.13
The supplied process ID references an LDEV that does not exist.14
The specified system is not known.18
Parameter or buffer out of bounds.22
Missing parameter.29
Security violation. The caller does not have read and execute access to the program file, or the caller
specified now = 1 without having a process access ID (PAID) equal to the super ID (255,255).
48
term (or the caller's home terminal if term was not specified) is not device type 6.190
Unable to communicate over this path.201
Network errors.240-249
All paths to the specified system are down.250
Bad parameter value. This error can occur when the supplied process ID is improperly formed.590
term
input
INT:ref:12
is the name of the debug home terminal. If omitted, the caller's home terminal is used.
now
input
INT:value
The caller's process access ID (PAID) must be the super ID (255, 255) to use this parameter.
If you supply 1, the process should be debugged immediately (even if it is currently executing
privileged code). If omitted, the normal debug sequence is executed.
Considerations
DEBUGPROCESS cannot be used on a high-PIN unnamed process. However, it can be used on a
high-PIN named process or process pair; process-id[3] must then contain either -1 or two blanks.
To invoke the debug facility on a high-PIN unnamed process, use the PROCESS_DEBUG_ procedure.
OSS Considerations
When used on an OSS process, DEBUGPROCESS forces the process into the Inspect debugger.
You can change the home terminal by specifying a valid value in the term parameter procedure.
Note that the home terminal is often the same device as the controlling terminal.
DEBUGPROCESS Procedure (Superseded by PROCESS_DEBUG_ Procedure) 257