Guardian Procedure Calls Reference Manual

terminal-name:length
input:input
STRING .EXT:ref:*, INT:value
if supplied and if length is not 0, is a file name that designates the terminal from which the
process is to be debugged. If used, the value of terminal-name must be exactly length
bytes long. If terminal-name is partially qualified, it is resolved using the contents of the
=_DEFAULTS DEFINE.
The default is the current home terminal of the process to be debugged.
now
input
INT:value
if 1, specifies that the process be debugged immediately (even if it is currently executing
privileged code); if omitted or 0, specifies that the normal debug sequence be executed.
The process access ID (PAID) of the calling process must be the super ID to use this parameter.
If the calling process runs only in privileged mode, now must be set to 1 or an error is returned.
Returned Value
INT
A file-system error code that indicates the outcome of the process debug attempt:
Debug request accepted. If the process to be debugged is not the calling process, the request might have
been queued.
0
Process does not exist.11
Security violation.48
Unable to communicate with the processor of the process.201
The target process runs in privileged mode and the now parameter was not set equal to 1.640
Considerations
• The caller of PROCESS_DEBUG_ must be the super ID, the group manager of the process
access ID, or a process with the same process access ID as the specified process or process
pair. For information about the process access ID, see the PROCESS_GETINFO_ procedure
General Considerations (page 1009) and the Guardian User's Guide.
The caller must be local to the same system as the specified process. A process is considered
to be local to the system on which its creator is local. A process is considered to be remote,
even if it is running on the local system, if its creator is remote. (In the same manner, a process
running on the local system whose creator is also running on the local system might still be
considered remote because it's creator's creator is remote.)
A remote process running on the local system can become a local process by successfully
logging on to the local system with a call to the USER_AUTHENTICATE_ procedure (or
VERIFYUSER). After a process logs on to the local system, any processes that it creates are
considered local.
• While a process is in the debug state, you can interactively display and modify the contents
of its registers and data area, and set breakpoints. To debug a program, you must have
execute access to run the program and read access to the program file.
1000 Guardian Procedure Calls (P)