bind #p /prog /prog/n/ctl /prog/n/dbgctl /prog/n/exception /prog/n/fd /prog/n/heap /prog/n/ns /prog/n/nsgrp /prog/n/pgrp /prog/n/stack /prog/n/status /prog/n/text /prog/n/wait ...
The read-only status file contains seven space-separated fields. The fields are: the process and process group identifiers, each 8 characters right justified; the user name, at least 10 characters left justified; cpu time in minutes, seconds and tenths of seconds; the process state, 10 characters left justified; the amount of memory used by the process in units of 1024 bytes, at least 5 characters, right justified, followed by a K; and the name of the current program module, up to 28 characters, left justified.
The read-only pgrp file contains the process group identifier, in decimal.
The read-only nsgrp file contains the namespace group identifier, in decimal.
The read-only ns file contains a set of mount and bind commands which describe the sys-bind(2) and mount operations used to construct the name space, in the format of namespace(6). The last line of the file is a cd command indicating the working directory.
The read-only wait file may be read to recover information about the exiting children of the process. A read of wait will block until a child of the process, created after wait was opened, exits. When such a child exits, it produces a string with three fields: the pid of the exiting process, a space, module name enclosed in "'s, a colon, and a possibly empty error message. The error message will contain at most 64 characters.
The read-only fd file describes the open file descriptors in the file descriptor group of the process. Each line describes an open file. The fields are: the file descriptor index, the open mode (r, w, rw); the type and number of the device; the path, version and type of the file's qid (see intro(5)); the file's atomic I/O unit, as defined in sys-iounit(2)); the file I/O offset in bytes; and the name with which it was opened.
The read-only exception file gives details of the last exception to occur in the process, if any. The fields are the program counter value when the exception occurred, the module it occurred in and the exception itself, each separated by a space. If none, the result is the empty string.
Messages written to the ctl file control the execution of the process.
The dbgctl file provides facilities for debugging a process. Messages written to the file control the execution of the process.
Reading dbgctl gives updates for some state transitions while the process is being debugged. Each update is terminated by a newline.
The read-only stack file contains the dynamic call stack trace. Each activation frame is described by one line with six fields, separated by a space: the frame pointer, program counter, module data pointer, and module code pointer, each 8 hexadecimal digits; the execution method for the module (0 means interpreted, 1 compiled); and the path name of the module. The top activation frame starts at offset 0.
The heap file may be queried to examine the state of the process. A data query contains an address, a period, a format character, and a count. An instruction query contains a pc, a plus, a mode address, a period, the format I, and a count. The addresses in the query may be decimal, hexadecimal preceded by 0x or 0X, or octal preceded by 0. Count gives the number of consecutive data items retrieved by reading heap starting at offset 0; the format varies according to the format character. All data items other than strings are terminated by a newline.
The following formats examine properties of specific 32-bit pointers.
The text file is currently unimplemented.
|PROG(3)||Rev: Tue Mar 31 02:42:38 GMT 2015|