Guardian Procedure Calls Reference Manual (G06.25+)

Guardian Procedure Calls (D-E)
Guardian Procedure Calls Reference Manual—522629-013
4-11
DEBUGPROCESS Procedure
(Superseded by PROCESS_DEBUG_ Procedure )
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.
To debug an OSS process, one of the following must be true:
•
The calling process must have appropriate privilege; that is, it must be locally
authenticated as the super ID on the system where the target process is executing.
•
All the following apply:
•
The caller’s effective user ID is the same as the saved user ID of the target
process.
•
The caller has sufficient “nonremoteness”; that is, the caller is locally
authenticated, or the target process is remotely authenticated and the caller is
authenticated from the viewpoint of the system where the target process is
executing.
•
The caller has read access to the program file and any library files.
•
The program does not contain PRIV or CALLABLE routines.
•
The target is not a system process.
•
The now parameter is not specified.
Only program file owners and users with appropriate privileges are able to debug
programs that set the user ID.