1 '\" te
2 .\" Copyright 1989 AT&T
3 .\" Copyright (c) 2006, Sun Microsystems, Inc. All Rights Reserved.
4 .\" Copyright 2015, Joyent, Inc.
5 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
6 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
7 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
8 .TH PROC 4 "May 19, 2014"
9 .SH NAME
10 proc \- /proc, the process file system
11 .SH DESCRIPTION
12 .LP
13 \fB/proc\fR is a file system that provides access to the state of each process
14 and light-weight process (lwp) in the system. The name of each entry in the
15 \fB/proc\fR directory is a decimal number corresponding to a process-ID. These
16 entries are themselves subdirectories. Access to process state is provided by
17 additional files contained within each subdirectory; the hierarchy is described
18 more completely below. In this document, ``\fB/proc\fR file'' refers to a
19 non-directory file within the hierarchy rooted at \fB/proc\fR. The owner of
20 each \fB/proc\fR file and subdirectory is determined by the user-ID of the
21 process.
22 .sp
23 .LP
24 \fB/proc\fR can be mounted on any mount point, in addition to the standard
25 \fB/proc\fR mount point, and can be mounted several places at once. Such
26 additional mounts are allowed in order to facilitate the confinement of
27 processes to subtrees of the file system via \fBchroot\fR(1M) and yet allow
28 such processes access to commands like \fBps\fR(1).
29 .sp
30 .LP
31 Standard system calls are used to access \fB/proc\fR files: \fBopen\fR(2),
32 \fBclose\fR(2), \fBread\fR(2), and \fBwrite\fR(2) (including \fBreadv\fR(2),
33 \fBwritev\fR(2), \fBpread\fR(2), and \fBpwrite\fR(2)). Most files describe
34 process state and can only be opened for reading. \fBctl\fR and \fBlwpctl\fR
35 (control) files permit manipulation of process state and can only be opened for
36 writing. \fBas\fR (address space) files contain the image of the running
37 process and can be opened for both reading and writing. An open for writing
38 allows process control; a read-only open allows inspection but not control. In
39 this document, we refer to the process as open for reading or writing if any of
40 its associated \fB/proc\fR files is open for reading or writing.
41 .sp
42 .LP
43 In general, more than one process can open the same \fB/proc\fR file at the
44 same time. \fIExclusive\fR \fIopen\fR is an advisory mechanism provided to
45 allow controlling processes to avoid collisions with each other. A process can
46 obtain exclusive control of a target process, with respect to other cooperating
47 processes, if it successfully opens any \fB/proc\fR file in the target process
48 for writing (the \fBas\fR or \fBctl\fR files, or the \fBlwpctl\fR file of any
49 lwp) while specifying \fBO_EXCL\fR in the \fBopen\fR(2). Such an open will fail
50 if the target process is already open for writing (that is, if an \fBas\fR,
51 \fBctl\fR, or \fBlwpctl\fR file is already open for writing). There can be any
52 number of concurrent read-only opens; \fBO_EXCL\fR is ignored on opens for
53 reading. It is recommended that the first open for writing by a controlling
54 process use the \fBO_EXCL\fR flag; multiple controlling processes usually
55 result in chaos.
56 .sp
57 .LP
58 If a process opens one of its own \fB/proc\fR files for writing, the open
59 succeeds regardless of \fBO_EXCL\fR and regardless of whether some other
60 process has the process open for writing. Self-opens do not count when another
61 process attempts an exclusive open. (A process cannot exclude a debugger by
62 opening itself for writing and the application of a debugger cannot prevent a
63 process from opening itself.) All self-opens for writing are forced to be
64 close-on-exec (see the \fBF_SETFD\fR operation of \fBfcntl\fR(2)).
65 .sp
66 .LP
67 Data may be transferred from or to any locations in the address space of the
68 traced process by applying \fBlseek\fR(2) to position the \fBas\fR file at the
69 virtual address of interest followed by \fBread\fR(2) or \fBwrite\fR(2) (or by
70 using \fBpread\fR(2) or \fBpwrite\fR(2) for the combined operation). The
71 address-map files \fB/proc/\fR\fIpid\fR\fB/map\fR and
72 \fB/proc/\fR\fIpid\fR\fB/xmap\fR can be read to determine the accessible areas
73 (mappings) of the address space. \fBI/O\fR transfers may span contiguous
74 mappings. An \fBI/O\fR request extending into an unmapped area is truncated at
75 the boundary. A write request beginning at an unmapped virtual address fails
76 with \fBEIO\fR; a read request beginning at an unmapped virtual address returns
77 zero (an end-of-file indication).
78 .sp
79 .LP
80 Information and control operations are provided through additional files.
81 \fB<procfs.h>\fR contains definitions of data structures and message formats
82 used with these files. Some of these definitions involve the use of sets of
83 flags. The set types \fBsigset_t\fR, \fBfltset_t\fR, and \fBsysset_t\fR
84 correspond, respectively, to signal, fault, and system call enumerations
85 defined in \fB<sys/signal.h>\fR, \fB<sys/fault.h>\fR, and
86 \fB<sys/syscall.h>\fR\&. Each set type is large enough to hold flags for its
87 own enumeration. Although they are of different sizes, they have a common
88 structure and can be manipulated by these macros:
89 .sp
90 .in +2
91 .nf
92 prfillset(&set); /* turn on all flags in set */
93 premptyset(&set); /* turn off all flags in set */
94 praddset(&set, flag); /* turn on the specified flag */
95 prdelset(&set, flag); /* turn off the specified flag */
96 r = prismember(&set, flag); /* != 0 iff flag is turned on */
97 .fi
98 .in -2
99
100 .sp
101 .LP
102 One of \fBprfillset()\fR or \fBpremptyset()\fR must be used to initialize
103 \fBset\fR before it is used in any other operation. \fBflag\fR must be a member
104 of the enumeration corresponding to \fBset\fR.
105 .sp
106 .LP
107 Every process contains at least one \fIlight-weight process\fR, or \fIlwp\fR.
108 Each lwp represents a flow of execution that is independently scheduled by the
109 operating system. All lwps in a process share its address space as well as many
110 other attributes. Through the use of \fBlwpctl\fR and \fBctl\fR files as
111 described below, it is possible to affect individual lwps in a process or to
112 affect all of them at once, depending on the operation.
113 .sp
114 .LP
115 When the process has more than one lwp, a representative lwp is chosen by the
116 system for certain process status files and control operations. The
117 representative lwp is a stopped lwp only if all of the process's lwps are
118 stopped; is stopped on an event of interest only if all of the lwps are so
119 stopped (excluding \fBPR_SUSPENDED\fR lwps); is in a \fBPR_REQUESTED\fR stop
120 only if there are no other events of interest to be found; or, failing
121 everything else, is in a \fBPR_SUSPENDED\fR stop (implying that the process is
122 deadlocked). See the description of the \fBstatus\fR file for definitions of
123 stopped states. See the \fBPCSTOP\fR control operation for the definition of
124 ``event of interest''.
125 .sp
126 .LP
127 The representative lwp remains fixed (it will be chosen again on the next
128 operation) as long as all of the lwps are stopped on events of interest or are
129 in a \fBPR_SUSPENDED\fR stop and the \fBPCRUN\fR control operation is not
130 applied to any of them.
131 .sp
132 .LP
133 When applied to the process control file, every \fB/proc\fR control operation
134 that must act on an lwp uses the same algorithm to choose which lwp to act
135 upon. Together with synchronous stopping (see \fBPCSET\fR), this enables a
136 debugger to control a multiple-lwp process using only the process-level status
137 and control files if it so chooses. More fine-grained control can be achieved
138 using the lwp-specific files.
139 .sp
140 .LP
141 The system supports two process data models, the traditional 32-bit data model
142 in which ints, longs and pointers are all 32 bits wide (the ILP32 data model),
143 and on some platforms the 64-bit data model in which longs and pointers, but
144 not ints, are 64 bits in width (the LP64 data model). In the LP64 data model
145 some system data types, notably \fBsize_t\fR, \fBoff_t\fR, \fBtime_t\fR and
146 \fBdev_t\fR, grow from 32 bits to 64 bits as well.
147 .sp
148 .LP
149 The \fB/proc\fR interfaces described here are available to both 32-bit and
150 64-bit controlling processes. However, many operations attempted by a 32-bit
151 controlling process on a 64-bit target process will fail with \fBEOVERFLOW\fR
152 because the address space range of a 32-bit process cannot encompass a 64-bit
153 process or because the data in some 64-bit system data type cannot be
154 compressed to fit into the corresponding 32-bit type without loss of
155 information. Operations that fail in this circumstance include reading and
156 writing the address space, reading the address-map files, and setting the
157 target process's registers. There is no restriction on operations applied by a
158 64-bit process to either a 32-bit or a 64-bit target processes.
159 .sp
160 .LP
161 The format of the contents of any \fB/proc\fR file depends on the data model of
162 the observer (the controlling process), not on the data model of the target
163 process. A 64-bit debugger does not have to translate the information it reads
164 from a \fB/proc\fR file for a 32-bit process from 32-bit format to 64-bit
165 format. However, it usually has to be aware of the data model of the target
166 process. The \fBpr_dmodel\fR field of the \fBstatus\fR files indicates the
167 target process's data model.
168 .sp
169 .LP
170 To help deal with system data structures that are read from 32-bit processes, a
171 64-bit controlling program can be compiled with the C preprocessor symbol
172 \fB_SYSCALL32\fR defined before system header files are included. This makes
173 explicit 32-bit fixed-width data structures (like \fBcstruct stat32\fR) visible
174 to the 64-bit program. See \fBtypes32.h\fR(3HEAD).
175 .SH DIRECTORY STRUCTURE
176 .LP
177 At the top level, the directory \fB/proc\fR contains entries each of which
178 names an existing process in the system. These entries are themselves
179 directories. Except where otherwise noted, the files described below can be
180 opened for reading only. In addition, if a process becomes a \fIzombie\fR (one
181 that has exited but whose parent has not yet performed a \fBwait\fR(3C) upon
182 it), most of its associated \fB/proc\fR files disappear from the hierarchy;
183 subsequent attempts to open them, or to read or write files opened before the
184 process exited, will elicit the error \fBENOENT\fR.
185 .sp
186 .LP
187 Although process state and consequently the contents of \fB/proc\fR files can
188 change from instant to instant, a single \fBread\fR(2) of a \fB/proc\fR file is
189 guaranteed to return a sane representation of state; that is, the read will be
190 atomic with respect to the state of the process. No such guarantee applies to
191 successive reads applied to a \fB/proc\fR file for a running process. In
192 addition, atomicity is not guaranteed for \fBI/O\fR applied to the \fBas\fR
193 (address-space) file for a running process or for a process whose address space
194 contains memory shared by another running process.
195 .sp
196 .LP
197 A number of structure definitions are used to describe the files. These
198 structures may grow by the addition of elements at the end in future releases
199 of the system and it is not legitimate for a program to assume that they will
200 not.
201 .SH STRUCTURE OF \fB/proc/\fR\fIpid\fR
202 .LP
203 A given directory \fB/proc/\fR\fIpid\fR contains the following entries. A
204 process can use the invisible alias \fB/proc/self\fR if it wishes to open one
205 of its own \fB/proc\fR files (invisible in the sense that the name ``self''
206 does not appear in a directory listing of \fB/proc\fR obtained from
207 \fBls\fR(1), \fBgetdents\fR(2), or \fBreaddir\fR(3C)).
208 .SS "contracts"
209 .LP
210 A directory containing references to the contracts held by the process. Each
211 entry is a symlink to the contract's directory under \fB/system/contract\fR.
212 See \fBcontract\fR(4).
213 .SS "as"
214 .LP
215 Contains the address-space image of the process; it can be opened for both
216 reading and writing. \fBlseek\fR(2) is used to position the file at the virtual
217 address of interest and then the address space can be examined or changed
218 through \fBread\fR(2) or \fBwrite\fR(2) (or by using \fBpread\fR(2) or
219 \fBpwrite\fR(2) for the combined operation).
220 .SS "ctl"
221 .LP
222 A write-only file to which structured messages are written directing the system
223 to change some aspect of the process's state or control its behavior in some
224 way. The seek offset is not relevant when writing to this file. Individual lwps
225 also have associated \fBlwpctl\fR files in the lwp subdirectories. A control
226 message may be written either to the process's \fBctl\fR file or to a specific
227 \fBlwpctl\fR file with operation-specific effects. The effect of a control
228 message is immediately reflected in the state of the process visible through
229 appropriate status and information files. The types of control messages are
230 described in detail later. See \fBCONTROL MESSAGES\fR.
231 .SS "status"
232 .LP
233 Contains state information about the process and the representative lwp. The
234 file contains a \fBpstatus\fR structure which contains an embedded
235 \fBlwpstatus\fR structure for the representative lwp, as follows:
236 .sp
237 .in +2
238 .nf
239 typedef struct pstatus {
240 int pr_flags; /* flags (see below) */
241 int pr_nlwp; /* number of active lwps in the process */
242 int pr_nzomb; /* number of zombie lwps in the process */
243 pid_tpr_pid; /* process id */
244 pid_tpr_ppid; /* parent process id */
245 pid_tpr_pgid; /* process group id */
246 pid_tpr_sid; /* session id */
247 id_t pr_aslwpid; /* obsolete */
248 id_t pr_agentid; /* lwp-id of the agent lwp, if any */
249 sigset_t pr_sigpend; /* set of process pending signals */
250 uintptr_t pr_brkbase; /* virtual address of the process heap */
251 size_t pr_brksize; /* size of the process heap, in bytes */
252 uintptr_t pr_stkbase; /* virtual address of the process stack */
253 size_tpr_stksize; /* size of the process stack, in bytes */
254 timestruc_t pr_utime; /* process user cpu time */
255 timestruc_t pr_stime; /* process system cpu time */
256 timestruc_t pr_cutime; /* sum of children's user times */
257 timestruc_t pr_cstime; /* sum of children's system times */
258 sigset_t pr_sigtrace; /* set of traced signals */
259 fltset_t pr_flttrace; /* set of traced faults */
260 sysset_t pr_sysentry; /* set of system calls traced on entry */
261 sysset_t pr_sysexit; /* set of system calls traced on exit */
262 char pr_dmodel; /* data model of the process */
263 taskid_t pr_taskid; /* task id */
264 projid_t pr_projid; /* project id */
265 zoneid_t pr_zoneid; /* zone id */
266 lwpstatus_t pr_lwp; /* status of the representative lwp */
267 } pstatus_t;
268 .fi
269 .in -2
270
271 .sp
272 .LP
273 \fBpr_flags\fR is a bit-mask holding the following process flags. For
274 convenience, it also contains the lwp flags for the representative lwp,
275 described later.
276 .sp
277 .ne 2
278 .na
279 \fB\fBPR_ISSYS\fR\fR
280 .ad
281 .RS 13n
282 process is a system process (see \fBPCSTOP\fR).
283 .RE
284
285 .sp
286 .ne 2
287 .na
288 \fB\fBPR_VFORKP\fR\fR
289 .ad
290 .RS 13n
291 process is the parent of a vforked child (see \fBPCWATCH\fR).
292 .RE
293
294 .sp
295 .ne 2
296 .na
297 \fB\fBPR_FORK\fR\fR
298 .ad
299 .RS 13n
300 process has its inherit-on-fork mode set (see \fBPCSET\fR).
301 .RE
302
303 .sp
304 .ne 2
305 .na
306 \fB\fBPR_RLC\fR\fR
307 .ad
308 .RS 13n
309 process has its run-on-last-close mode set (see \fBPCSET\fR).
310 .RE
311
312 .sp
313 .ne 2
314 .na
315 \fB\fBPR_KLC\fR\fR
316 .ad
317 .RS 13n
318 process has its kill-on-last-close mode set (see \fBPCSET\fR).
319 .RE
320
321 .sp
322 .ne 2
323 .na
324 \fB\fBPR_ASYNC\fR\fR
325 .ad
326 .RS 13n
327 process has its asynchronous-stop mode set (see \fBPCSET\fR).
328 .RE
329
330 .sp
331 .ne 2
332 .na
333 \fB\fBPR_MSACCT\fR\fR
334 .ad
335 .RS 13n
336 Set by default in all processes to indicate that microstate accounting is
337 enabled. However, this flag has been deprecated and no longer has any effect.
338 Microstate accounting may not be disabled; however, it is still possible to
339 toggle the flag.
340 .RE
341
342 .sp
343 .ne 2
344 .na
345 \fB\fBPR_MSFORK\fR\fR
346 .ad
347 .RS 13n
348 Set by default in all processes to indicate that microstate accounting will be
349 enabled for processes that this parent forks(). However, this flag has been
350 deprecated and no longer has any effect. It is possible to toggle this flag;
351 however, it is not possible to disable microstate accounting.
352 .RE
353
354 .sp
355 .ne 2
356 .na
357 \fB\fBPR_BPTADJ\fR\fR
358 .ad
359 .RS 13n
360 process has its breakpoint adjustment mode set (see \fBPCSET\fR).
361 .RE
362
363 .sp
364 .ne 2
365 .na
366 \fB\fBPR_PTRACE\fR\fR
367 .ad
368 .RS 13n
369 process has its ptrace-compatibility mode set (see \fBPCSET\fR).
370 .RE
371
372 .sp
373 .LP
374 \fBpr_nlwp\fR is the total number of active lwps in the process. pr_nzomb is
375 the total number of zombie lwps in the process. A zombie lwp is a non-detached
376 lwp that has terminated but has not been reaped with \fBthr_join\fR(3C) or
377 \fBpthread_join\fR(3C).
378 .sp
379 .LP
380 \fBpr_pid\fR, \fBpr_ppid\fR, \fBpr_pgid\fR, and \fBpr_sid\fR are, respectively,
381 the process ID, the ID of the process's parent, the process's process group ID,
382 and the process's session ID.
383 .sp
384 .LP
385 \fBpr_aslwpid\fR is obsolete and is always zero.
386 .sp
387 .LP
388 \fBpr_agentid\fR is the lwp-ID for the \fB/proc\fR agent lwp (see the
389 \fBPCAGENT\fR control operation). It is zero if there is no agent lwp in the
390 process.
391 .sp
392 .LP
393 \fBpr_sigpend\fR identifies asynchronous signals pending for the process.
394 .sp
395 .LP
396 \fBpr_brkbase\fR is the virtual address of the process heap and
397 \fBpr_brksize\fR is its size in bytes. The address formed by the sum of these
398 values is the process \fBbreak\fR (see \fBbrk\fR(2)). \fBpr_stkbase\fR and
399 \fBpr_stksize\fR are, respectively, the virtual address of the process stack
400 and its size in bytes. (Each lwp runs on a separate stack; the distinguishing
401 characteristic of the process stack is that the operating system will grow it
402 when necessary.)
403 .sp
404 .LP
405 \fBpr_utime\fR, \fBpr_stime\fR, \fBpr_cutime\fR, and \fBpr_cstime\fR are,
406 respectively, the user \fBCPU\fR and system \fBCPU\fR time consumed by the
407 process, and the cumulative user \fBCPU\fR and system \fBCPU\fR time consumed
408 by the process's children, in seconds and nanoseconds.
409 .sp
410 .LP
411 \fBpr_sigtrace\fR and \fBpr_flttrace\fR contain, respectively, the set of
412 signals and the set of hardware faults that are being traced (see
413 \fBPCSTRACE\fR and \fBPCSFAULT\fR).
414 .sp
415 .LP
416 \fBpr_sysentry\fR and \fBpr_sysexit\fR contain, respectively, the sets of
417 system calls being traced on entry and exit (see \fBPCSENTRY\fR and
418 \fBPCSEXIT\fR).
419 .sp
420 .LP
421 \fBpr_dmodel\fR indicates the data model of the process. Possible values are:
422 .sp
423 .ne 2
424 .na
425 \fB\fBPR_MODEL_ILP32\fR\fR
426 .ad
427 .RS 19n
428 process data model is ILP32.
429 .RE
430
431 .sp
432 .ne 2
433 .na
434 \fB\fBPR_MODEL_LP64\fR\fR
435 .ad
436 .RS 19n
437 process data model is LP64.
438 .RE
439
440 .sp
441 .ne 2
442 .na
443 \fB\fBPR_MODEL_NATIVE\fR\fR
444 .ad
445 .RS 19n
446 process data model is native.
447 .RE
448
449 .sp
450 .LP
451 The \fBpr_taskid\fR, \fBpr_projid\fR, and \fBpr_zoneid\fR fields contain
452 respectively, the numeric \fBID\fRs of the task, project, and zone in which the
453 process was running.
454 .sp
455 .LP
456 The constant \fBPR_MODEL_NATIVE\fR reflects the data model of the controlling
457 process, \fIthat is\fR, its value is \fBPR_MODEL_ILP32\fR or
458 \fBPR_MODEL_LP64\fR according to whether the controlling process has been
459 compiled as a 32-bit program or a 64-bit program, respectively.
460 .sp
461 .LP
462 \fBpr_lwp\fR contains the status information for the representative lwp:
463 .sp
464 .in +2
465 .nf
466 typedef struct lwpstatus {
467 int pr_flags; /* flags (see below) */
468 id_t pr_lwpid; /* specific lwp identifier */
469 short pr_why; /* reason for lwp stop, if stopped */
470 short pr_what; /* more detailed reason */
471 short pr_cursig; /* current signal, if any */
472 siginfo_t pr_info; /* info associated with signal or fault */
473 sigset_t pr_lwppend; /* set of signals pending to the lwp */
474 sigset_t pr_lwphold; /* set of signals blocked by the lwp */
475 struct sigaction pr_action;/* signal action for current signal */
476 stack_t pr_altstack; /* alternate signal stack info */
477 uintptr_t pr_oldcontext; /* address of previous ucontext */
478 short pr_syscall; /* system call number (if in syscall) */
479 short pr_nsysarg; /* number of arguments to this syscall */
480 int pr_errno; /* errno for failed syscall */
481 long pr_sysarg[PRSYSARGS]; /* arguments to this syscall */
482 long pr_rval1; /* primary syscall return value */
483 long pr_rval2; /* second syscall return value, if any */
484 char pr_clname[PRCLSZ]; /* scheduling class name */
485 timestruc_t pr_tstamp; /* real-time time stamp of stop */
486 timestruc_t pr_utime; /* lwp user cpu time */
487 timestruc_t pr_stime; /* lwp system cpu time */
488 uintptr_t pr_ustack; /* stack boundary data (stack_t) address */
489 ulong_t pr_instr; /* current instruction */
490 prgregset_t pr_reg; /* general registers */
491 prfpregset_t pr_fpreg; /* floating-point registers */
492 } lwpstatus_t;
493 .fi
494 .in -2
495
496 .sp
497 .LP
498 \fBpr_flags\fR is a bit-mask holding the following lwp flags. For convenience,
499 it also contains the process flags, described previously.
500 .sp
501 .ne 2
502 .na
503 \fB\fBPR_STOPPED\fR\fR
504 .ad
505 .RS 14n
506 The lwp is stopped.
507 .RE
508
509 .sp
510 .ne 2
511 .na
512 \fB\fBPR_ISTOP\fR\fR
513 .ad
514 .RS 14n
515 The lwp is stopped on an event of interest (see \fBPCSTOP\fR).
516 .RE
517
518 .sp
519 .ne 2
520 .na
521 \fB\fBPR_DSTOP\fR\fR
522 .ad
523 .RS 14n
524 The lwp has a stop directive in effect (see \fBPCSTOP\fR).
525 .RE
526
527 .sp
528 .ne 2
529 .na
530 \fB\fBPR_STEP\fR\fR
531 .ad
532 .RS 14n
533 The lwp has a single-step directive in effect (see \fBPCRUN\fR).
534 .RE
535
536 .sp
537 .ne 2
538 .na
539 \fB\fBPR_ASLEEP\fR\fR
540 .ad
541 .RS 14n
542 The lwp is in an interruptible sleep within a system call.
543 .RE
544
545 .sp
546 .ne 2
547 .na
548 \fB\fBPR_PCINVAL\fR\fR
549 .ad
550 .RS 14n
551 The lwp's current instruction (\fBpr_instr\fR) is undefined.
552 .RE
553
554 .sp
555 .ne 2
556 .na
557 \fB\fBPR_DETACH\fR\fR
558 .ad
559 .RS 14n
560 This is a detached lwp (see \fBpthread_create\fR(3C) and
561 \fBpthread_join\fR(3C)).
562 .RE
563
564 .sp
565 .ne 2
566 .na
567 \fB\fBPR_DAEMON\fR\fR
568 .ad
569 .RS 14n
570 This is a daemon lwp (see \fBpthread_create\fR(3C)).
571 .RE
572
573 .sp
574 .ne 2
575 .na
576 \fB\fBPR_ASLWP\fR\fR
577 .ad
578 .RS 14n
579 This flag is obsolete and is never set.
580 .RE
581
582 .sp
583 .ne 2
584 .na
585 \fB\fBPR_AGENT\fR\fR
586 .ad
587 .RS 14n
588 This is the \fB/proc\fR agent lwp for the process.
589 .RE
590
591 .sp
592 .LP
593 \fBpr_lwpid\fR names the specific lwp.
594 .sp
595 .LP
596 \fBpr_why\fR and \fBpr_what\fR together describe, for a stopped lwp, the reason
597 for the stop. Possible values of \fBpr_why\fR and the associated \fBpr_what\fR
598 are:
599 .sp
600 .ne 2
601 .na
602 \fB\fBPR_REQUESTED\fR\fR
603 .ad
604 .RS 17n
605 indicates that the stop occurred in response to a stop directive, normally
606 because \fBPCSTOP\fR was applied or because another lwp stopped on an event of
607 interest and the asynchronous-stop flag (see \fBPCSET\fR) was not set for the
608 process. \fBpr_what\fR is unused in this case.
609 .RE
610
611 .sp
612 .ne 2
613 .na
614 \fB\fBPR_SIGNALLED\fR\fR
615 .ad
616 .RS 17n
617 indicates that the lwp stopped on receipt of a signal (see \fBPCSTRACE\fR);
618 \fBpr_what\fR holds the signal number that caused the stop (for a newly-stopped
619 lwp, the same value is in \fBpr_cursig\fR).
620 .RE
621
622 .sp
623 .ne 2
624 .na
625 \fB\fBPR_FAULTED\fR\fR
626 .ad
627 .RS 17n
628 indicates that the lwp stopped on incurring a hardware fault (see
629 \fBPCSFAULT\fR); \fBpr_what\fR holds the fault number that caused the stop.
630 .RE
631
632 .sp
633 .ne 2
634 .na
635 \fB\fBPR_SYSENTRY\fR\fR
636 .ad
637 .br
638 .na
639 \fB\fBPR_SYSEXIT\fR\fR
640 .ad
641 .RS 17n
642 indicate a stop on entry to or exit from a system call (see \fBPCSENTRY\fR and
643 \fBPCSEXIT\fR); \fBpr_what\fR holds the system call number.
644 .RE
645
646 .sp
647 .ne 2
648 .na
649 \fB\fBPR_JOBCONTROL\fR\fR
650 .ad
651 .RS 17n
652 indicates that the lwp stopped due to the default action of a job control stop
653 signal (see \fBsigaction\fR(2)); \fBpr_what\fR holds the stopping signal
654 number.
655 .RE
656
657 .sp
658 .ne 2
659 .na
660 \fB\fBPR_SUSPENDED\fR\fR
661 .ad
662 .RS 17n
663 indicates that the lwp stopped due to internal synchronization of lwps within
664 the process. \fBpr_what\fR is unused in this case.
665 .RE
666
667 .sp
668 .ne 2
669 .na
670 \fB\fBPR_BRAND\fR\fR
671 .ad
672 .RS 17n
673 indicates that the lwp stopped for a brand-specific reason. Interpretation
674 of the value of \fBpr_what\fR depends on which zone brand is in use. It is
675 not generally expected that an lwp stopped in this state will be restarted
676 by native \fBproc\fR(4) consumers.
677 .RE
678
679 .sp
680 .LP
681 \fBpr_cursig\fR names the current signal, that is, the next signal to be
682 delivered to the lwp, if any. \fBpr_info\fR, when the lwp is in a
683 \fBPR_SIGNALLED\fR or \fBPR_FAULTED\fR stop, contains additional information
684 pertinent to the particular signal or fault (see \fB<sys/siginfo.h>\fR).
685 .sp
686 .LP
687 \fBpr_lwppend\fR identifies any synchronous or directed signals pending for the
688 lwp. \fBpr_lwphold\fR identifies those signals whose delivery is being blocked
689 by the lwp (the signal mask).
690 .sp
691 .LP
692 \fBpr_action\fR contains the signal action information pertaining to the
693 current signal (see \fBsigaction\fR(2)); it is undefined if \fBpr_cursig\fR is
694 zero. \fBpr_altstack\fR contains the alternate signal stack information for the
695 lwp (see \fBsigaltstack\fR(2)).
696 .sp
697 .LP
698 \fBpr_oldcontext\fR, if not zero, contains the address on the lwp stack of a
699 \fBucontext\fR structure describing the previous user-level context (see
700 \fBucontext.h\fR(3HEAD)). It is non-zero only if the lwp is executing in the
701 context of a signal handler.
702 .sp
703 .LP
704 \fBpr_syscall\fR is the number of the system call, if any, being executed by
705 the lwp; it is non-zero if and only if the lwp is stopped on \fBPR_SYSENTRY\fR
706 or \fBPR_SYSEXIT\fR, or is asleep within a system call ( \fBPR_ASLEEP\fR is
707 set). If \fBpr_syscall\fR is non-zero, \fBpr_nsysarg\fR is the number of
708 arguments to the system call and \fBpr_sysarg\fR contains the actual arguments.
709 .sp
710 .LP
711 \fBpr_rval1\fR, \fBpr_rval2\fR, and \fBpr_errno\fR are defined only if the lwp
712 is stopped on \fBPR_SYSEXIT\fR or if the \fBPR_VFORKP\fR flag is set. If
713 \fBpr_errno\fR is zero, \fBpr_rval1\fR and \fBpr_rval2\fR contain the return
714 values from the system call. Otherwise, \fBpr_errno\fR contains the error
715 number for the failing system call (see \fB<sys/errno.h>\fR).
716 .sp
717 .LP
718 \fBpr_clname\fR contains the name of the lwp's scheduling class.
719 .sp
720 .LP
721 \fBpr_tstamp\fR, if the lwp is stopped, contains a time stamp marking when the
722 lwp stopped, in real time seconds and nanoseconds since an arbitrary time in
723 the past.
724 .sp
725 .LP
726 \fBpr_utime\fR is the amount of user level CPU time used by this LWP.
727 .sp
728 .LP
729 \fBpr_stime\fR is the amount of system level CPU time used by this LWP.
730 .sp
731 .LP
732 \fBpr_ustack\fR is the virtual address of the \fBstack_t\fR that contains the
733 stack boundaries for this LWP. See \fBgetustack\fR(2) and
734 \fB_stack_grow\fR(3C).
735 .sp
736 .LP
737 \fBpr_instr\fR contains the machine instruction to which the lwp's program
738 counter refers. The amount of data retrieved from the process is
739 machine-dependent. On SPARC based machines, it is a 32-bit word. On x86-based
740 machines, it is a single byte. In general, the size is that of the machine's
741 smallest instruction. If \fBPR_PCINVAL\fR is set, \fBpr_instr\fR is undefined;
742 this occurs whenever the lwp is not stopped or when the program counter refers
743 to an invalid virtual address.
744 .sp
745 .LP
746 \fBpr_reg\fR is an array holding the contents of a stopped lwp's general
747 registers.
748 .sp
749 .ne 2
750 .na
751 \fBSPARC\fR
752 .ad
753 .RS 21n
754 On SPARC-based machines, the predefined constants \fBR_G0\fR ... \fBR_G7\fR,
755 \fBR_O0\fR ... \fBR_O7\fR, \fBR_L0\fR ... \fBR_L7\fR, \fBR_I0\fR ...
756 \fBR_I7\fR, \fBR_PC\fR, \fBR_nPC\fR, and \fBR_Y\fR can be used as indices to
757 refer to the corresponding registers; previous register windows can be read
758 from their overflow locations on the stack (however, see the \fBgwindows\fR
759 file in the \fB/proc/\fR\fIpid\fR\fB/lwp/\fR\fIlwpid\fR subdirectory).
760 .RE
761
762 .sp
763 .ne 2
764 .na
765 \fBSPARC V8 (32-bit)\fR
766 .ad
767 .RS 21n
768 For SPARC V8 (32-bit) controlling processes, the predefined constants
769 \fBR_PSR\fR, \fBR_WIM\fR, and \fBR_TBR\fR can be used as indices to refer to
770 the corresponding special registers. For SPARC V9 (64-bit) controlling
771 processes, the predefined constants \fBR_CCR\fR, \fBR_ASI\fR, and \fBR_FPRS\fR
772 can be used as indices to refer to the corresponding special registers.
773 .RE
774
775 .sp
776 .ne 2
777 .na
778 \fBx86 (32-bit)\fR
779 .ad
780 .RS 21n
781 For 32-bit x86 processes, the predefined constants listed belowcan be used as
782 indices to refer to the corresponding registers.
783 .sp
784 .in +2
785 .nf
786 SS
787 UESP
788 EFL
789 CS
790 EIP
791 ERR
792 TRAPNO
793 EAX
794 ECX
795 EDX
796 EBX
797 ESP
798 EBP
799 ESI
800 EDI
801 DS
802 ES
803 GS
804 .fi
805 .in -2
806
807 The preceding constants are listed in \fB<sys/regset.h>\fR\&.
808 .sp
809 Note that a 32-bit process can run on an x86 64-bit system, using the constants
810 listed above.
811 .RE
812
813 .sp
814 .ne 2
815 .na
816 \fBx86 (64-bit)\fR
817 .ad
818 .RS 21n
819 To read the registers of a 32- \fBor\fR a 64-bit process, a 64-bit x86 process
820 should use the predefined constants listed below.
821 .sp
822 .in +2
823 .nf
824 REG_GSBASE
825 REG_FSBASE
826 REG_DS
827 REG_ES
828 REG_GS
829 REG_FS
830 REG_SS
831 REG_RSP
832 REG_RFL
833 REG_CS
834 REG_RIP
835 REG_ERR
836 REG_TRAPNO
837 REG_RAX
838 REG_RCX
839 REG_RDX
840 REG_RBX
841 REG_RBP
842 REG_RSI
843 REG_RDI
844 REG_R8
845 REG_R9
846 REG_R10
847 REG_R11
848 REG_R12
849 REG_R13
850 REG_R14
851 REG_R15
852 .fi
853 .in -2
854
855 The preceding constants are listed in \fB<sys/regset.h>\fR\&.
856 .RE
857
858 .sp
859 .LP
860 \fBpr_fpreg\fR is a structure holding the contents of the floating-point
861 registers.
862 .sp
863 .LP
864 SPARC registers, both general and floating-point, as seen by a 64-bit
865 controlling process are the V9 versions of the registers, even if the target
866 process is a 32-bit (V8) process. V8 registers are a subset of the V9
867 registers.
868 .sp
869 .LP
870 If the lwp is not stopped, all register values are undefined.
871 .SS "psinfo"
872 .LP
873 Contains miscellaneous information about the process and the representative lwp
874 needed by the \fBps\fR(1) command. \fBpsinfo\fR remains accessible after a
875 process becomes a \fIzombie\fR. The file contains a \fBpsinfo\fR structure
876 which contains an embedded \fBlwpsinfo\fR structure for the representative lwp,
877 as follows:
878 .sp
879 .in +2
880 .nf
881 typedef struct psinfo {
882 int pr_flag; /* process flags (DEPRECATED: see below) */
883 int pr_nlwp; /* number of active lwps in the process */
884 int pr_nzomb; /* number of zombie lwps in the process */
885 pid_t pr_pid; /* process id */
886 pid_t pr_ppid; /* process id of parent */
887 pid_t pr_pgid; /* process id of process group leader */
888 pid_t pr_sid; /* session id */
889 uid_t pr_uid; /* real user id */
890 uid_t pr_euid; /* effective user id */
891 gid_t pr_gid; /* real group id */
892 gid_t pr_egid; /* effective group id */
893 uintptr_t pr_addr; /* address of process */
894 size_t pr_size; /* size of process image in Kbytes */
895 size_t pr_rssize; /* resident set size in Kbytes */
896 dev_t pr_ttydev; /* controlling tty device (or PRNODEV) */
897 ushort_t pr_pctcpu; /* % of recent cpu time used by all lwps */
898 ushort_t pr_pctmem; /* % of system memory used by process */
899 timestruc_t pr_start; /* process start time, from the epoch */
900 timestruc_t pr_time; /* cpu time for this process */
901 timestruc_t pr_ctime; /* cpu time for reaped children */
902 char pr_fname[PRFNSZ]; /* name of exec'ed file */
903 char pr_psargs[PRARGSZ]; /* initial characters of arg list */
904 int pr_wstat; /* if zombie, the wait() status */
905 int pr_argc; /* initial argument count */
906 uintptr_t pr_argv; /* address of initial argument vector */
907 uintptr_t pr_envp; /* address of initial environment vector */
908 char pr_dmodel; /* data model of the process */
909 lwpsinfo_t pr_lwp; /* information for representative lwp */
910 taskid_t pr_taskid; /* task id */
911 projid_t pr_projid; /* project id */
912 poolid_t pr_poolid; /* pool id */
913 zoneid_t pr_zoneid; /* zone id */
914 ctid_t pr_contract; /* process contract id */
915 } psinfo_t;
916 .fi
917 .in -2
918
919 .sp
920 .LP
921 Some of the entries in \fBpsinfo\fR, such as \fBpr_addr\fR, refer to internal
922 kernel data structures and should not be expected to retain their meanings
923 across different versions of the operating system.
924 .sp
925 .LP
926 \fBpsinfo_t.pr_flag\fR is a deprecated interface that should no longer be used.
927 Applications currently relying on the \fBSSYS\fR bit in \fBpr_flag\fR should
928 migrate to checking \fBPR_ISSYS\fR in the \fBpstatus\fR structure's
929 \fBpr_flags\fR field.
930 .sp
931 .LP
932 \fBpr_pctcpu\fR and \fBpr_pctmem\fR are 16-bit binary fractions in the range
933 0.0 to 1.0 with the binary point to the right of the high-order bit (1.0 ==
934 0x8000). \fBpr_pctcpu\fR is the summation over all lwps in the process.
935 .sp
936 .LP
937 The \fBpr_fname\fR and \fBpr_psargs\fR are writable by the owner of the
938 process. To write to them, the \fBpsinfo\fR file should be open for writing
939 and the desired value for the field should be written at the file offset
940 that corresponds to the member of structure. No other entry may be written
941 to; if a write is attempted to an offset that does not represent one of
942 these two memers, or if the size of the write is not exactly the size of
943 the member being written, no bytes will be written and zero will be returned.
944 .sp
945 .LP
946 \fBpr_lwp\fR contains the \fBps\fR(1) information for the representative lwp.
947 If the process is a \fIzombie\fR, \fBpr_nlwp\fR, \fBpr_nzomb\fR, and
948 \fBpr_lwp.pr_lwpid\fR are zero and the other fields of \fBpr_lwp\fR are
949 undefined:
950 .sp
951 .in +2
952 .nf
953 typedef struct lwpsinfo {
954 int pr_flag; /* lwp flags (DEPRECATED: see below) */
955 id_t pr_lwpid; /* lwp id */
956 uintptr_t pr_addr; /* internal address of lwp */
957 uintptr_t pr_wchan; /* wait addr for sleeping lwp */
958 char pr_stype; /* synchronization event type */
959 char pr_state; /* numeric lwp state */
960 char pr_sname; /* printable character for pr_state */
961 char pr_nice; /* nice for cpu usage */
962 short pr_syscall; /* system call number (if in syscall) */
963 char pr_oldpri; /* pre-SVR4, low value is high priority */
964 char pr_cpu; /* pre-SVR4, cpu usage for scheduling */
965 int pr_pri; /* priority, high value = high priority */
966 ushort_t pr_pctcpu; /* % of recent cpu time used by this lwp */
967 timestruc_t pr_start; /* lwp start time, from the epoch */
968 timestruc_t pr_time; /* cpu time for this lwp */
969 char pr_clname[PRCLSZ]; /* scheduling class name */
970 char pr_name[PRFNSZ]; /* name of system lwp */
971 processorid_t pr_onpro; /* processor which last ran this lwp */
972 processorid_t pr_bindpro;/* processor to which lwp is bound */
973 psetid_t pr_bindpset; /* processor set to which lwp is bound */
974 lgrp_id_t pr_lgrp /* home lgroup */
975 } lwpsinfo_t;
976 .fi
977 .in -2
978
979 .sp
980 .LP
981 Some of the entries in \fBlwpsinfo\fR, such as \fBpr_addr\fR, \fBpr_wchan\fR,
982 \fBpr_stype\fR, \fBpr_state\fR, and \fBpr_name\fR, refer to internal kernel
983 data structures and should not be expected to retain their meanings across
984 different versions of the operating system.
985 .sp
986 .LP
987 \fBlwpsinfo_t.pr_flag\fR is a deprecated interface that should no longer be
988 used.
989 .sp
990 .LP
991 \fBpr_pctcpu\fR is a 16-bit binary fraction, as described above. It represents
992 the \fBCPU\fR time used by the specific lwp. On a multi-processor machine, the
993 maximum value is 1/N, where N is the number of \fBCPU\fRs.
994 .sp
995 .LP
996 \fBpr_contract\fR is the id of the process contract of which the process is a
997 member. See \fBcontract\fR(4) and \fBprocess\fR(4).
998 .SS "cred"
999 .LP
1000 Contains a description of the credentials associated with the process:
1001 .sp
1002 .in +2
1003 .nf
1004 typedef struct prcred {
1005 uid_t pr_euid; /* effective user id */
1006 uid_t pr_ruid; /* real user id */
1007 uid_t pr_suid; /* saved user id (from exec) */
1008 gid_t pr_egid; /* effective group id */
1009 gid_t pr_rgid; /* real group id */
1010 gid_t pr_sgid; /* saved group id (from exec) */
1011 int pr_ngroups; /* number of supplementary groups */
1012 gid_t pr_groups[1]; /* array of supplementary groups */
1013 } prcred_t;
1014 .fi
1015 .in -2
1016 .sp
1017
1018 .sp
1019 .LP
1020 The array of associated supplementary groups in \fBpr_groups\fR is of variable
1021 length; the \fBcred\fR file contains all of the supplementary groups.
1022 \fBpr_ngroups\fR indicates the number of supplementary groups. (See also the
1023 \fBPCSCRED\fR and \fBPCSCREDX\fR control operations.)
1024 .SS "priv"
1025 .LP
1026 Contains a description of the privileges associated with the process:
1027 .sp
1028 .in +2
1029 .nf
1030 typedef struct prpriv {
1031 uint32_t pr_nsets; /* number of privilege set */
1032 uint32_t pr_setsize; /* size of privilege set */
1033 uint32_t pr_infosize; /* size of supplementary data */
1034 priv_chunk_t pr_sets[1]; /* array of sets */
1035 } prpriv_t;
1036 .fi
1037 .in -2
1038
1039 .sp
1040 .LP
1041 The actual dimension of the \fBpr_sets\fR[] field is
1042 .sp
1043 .in +2
1044 .nf
1045 pr_sets[pr_nsets][pr_setsize]
1046 .fi
1047 .in -2
1048
1049 .sp
1050 .LP
1051 which is followed by additional information about the process state
1052 \fBpr_infosize\fR bytes in size.
1053 .sp
1054 .LP
1055 The full size of the structure can be computed using
1056 \fBPRIV_PRPRIV_SIZE\fR(\fBprpriv_t *\fR).
1057 .SS "sigact"
1058 .LP
1059 Contains an array of \fBsigaction structures\fR describing the current
1060 dispositions of all signals associated with the traced process (see
1061 \fBsigaction\fR(2)). Signal numbers are displaced by 1 from array indices, so
1062 that the action for signal number \fIn\fR appears in position \fIn\fR-1 of the
1063 array.
1064 .SS "auxv"
1065 .LP
1066 Contains the initial values of the process's aux vector in an array of
1067 \fBauxv_t\fR structures (see \fB<sys/auxv.h>\fR). The values are those that
1068 were passed by the operating system as startup information to the dynamic
1069 linker.
1070 .SS "argv"
1071 .LP
1072 Contains the concatenation of each of the argument strings, including their
1073 \fBNUL\fR terminators, in the argument vector (\fBargv\fR) for the process. If
1074 the process has modified either its argument vector, or the contents of any of
1075 the strings referenced by that vector, those changes will be visible here.
1076 .SS "ldt"
1077 .LP
1078 This file exists only on x86-based machines. It is non-empty only if the
1079 process has established a local descriptor table (\fBLDT\fR). If non-empty, the
1080 file contains the array of currently active \fBLDT\fR entries in an array of
1081 elements of type \fBstruct ssd\fR, defined in \fB<sys/sysi86.h>\fR, one element
1082 for each active \fBLDT\fR entry.
1083 .SS "map, xmap"
1084 .LP
1085 Contain information about the virtual address map of the process. The map file
1086 contains an array of \fBprmap\fR structures while the xmap file contains an
1087 array of \fBprxmap\fR structures. Each structure describes a contiguous virtual
1088 address region in the address space of the traced process:
1089 .sp
1090 .in +2
1091 .nf
1092 typedef struct prmap {
1093 uintptr_tpr_vaddr; /* virtual address of mapping */
1094 size_t pr_size; /* size of mapping in bytes */
1095 char pr_mapname[PRMAPSZ]; /* name in /proc/pid/object */
1096 offset_t pr_offset; /* offset into mapped object, if any */
1097 int pr_mflags; /* protection and attribute flags */
1098 int pr_pagesize; /* pagesize for this mapping in bytes */
1099 int pr_shmid; /* SysV shared memory identifier */
1100 } prmap_t;
1101 .fi
1102 .in -2
1103 .sp
1104
1105 .sp
1106 .in +2
1107 .nf
1108 typedef struct prxmap {
1109 uintptr_t pr_vaddr; /* virtual address of mapping */
1110 size_t pr_size; /* size of mapping in bytes */
1111 char pr_mapname[PRMAPSZ]; /* name in /proc/pid/object */
1112 offset_t pr_offset; /* offset into mapped object, if any */
1113 int pr_mflags; /* protection and attribute flags */
1114 int pr_pagesize; /* pagesize for this mapping in bytes */
1115 int pr_shmid; /* SysV shared memory identifier */
1116 dev_t pr_dev; /* device of mapped object, if any */
1117 uint64_t pr_ino; /* inode of mapped object, if any */
1118 size_t pr_rss; /* pages of resident memory */
1119 size_t pr_anon; /* pages of resident anonymous memory */
1120 size_t pr_locked; /* pages of locked memory */
1121 uint64_t pr_hatpagesize; /* pagesize of mapping */
1122 } prxmap_t;
1123 .fi
1124 .in -2
1125 .sp
1126
1127 .sp
1128 .LP
1129 \fBpr_vaddr\fR is the virtual address of the mapping within the traced process
1130 and \fBpr_size\fR is its size in bytes. \fBpr_mapname\fR, if it does not
1131 contain a null string, contains the name of a file in the \fBobject\fR
1132 directory (see below) that can be opened read-only to obtain a file descriptor
1133 for the mapped file associated with the mapping. This enables a debugger to
1134 find object file symbol tables without having to know the real path names of
1135 the executable file and shared libraries of the process. \fBpr_offset\fR is the
1136 64-bit offset within the mapped file (if any) to which the virtual address is
1137 mapped.
1138 .sp
1139 .LP
1140 \fBpr_mflags\fR is a bit-mask of protection and attribute flags:
1141 .sp
1142 .ne 2
1143 .na
1144 \fB\fBMA_READ\fR\fR
1145 .ad
1146 .RS 17n
1147 mapping is readable by the traced process.
1148 .RE
1149
1150 .sp
1151 .ne 2
1152 .na
1153 \fB\fBMA_WRITE\fR\fR
1154 .ad
1155 .RS 17n
1156 mapping is writable by the traced process.
1157 .RE
1158
1159 .sp
1160 .ne 2
1161 .na
1162 \fB\fBMA_EXEC\fR\fR
1163 .ad
1164 .RS 17n
1165 mapping is executable by the traced process.
1166 .RE
1167
1168 .sp
1169 .ne 2
1170 .na
1171 \fB\fBMA_SHARED\fR\fR
1172 .ad
1173 .RS 17n
1174 mapping changes are shared by the mapped object.
1175 .RE
1176
1177 .sp
1178 .ne 2
1179 .na
1180 \fB\fBMA_ISM\fR\fR
1181 .ad
1182 .RS 17n
1183 mapping is intimate shared memory (shared MMU resources)
1184 .RE
1185
1186 .sp
1187 .ne 2
1188 .na
1189 \fB\fBMAP_NORESERVE\fR\fR
1190 .ad
1191 .RS 17n
1192 mapping does not have swap space reserved (mapped with MAP_NORESERVE)
1193 .RE
1194
1195 .sp
1196 .ne 2
1197 .na
1198 \fB\fBMA_SHM\fR\fR
1199 .ad
1200 .RS 17n
1201 mapping System V shared memory
1202 .RE
1203
1204 .sp
1205 .LP
1206 A contiguous area of the address space having the same underlying mapped object
1207 may appear as multiple mappings due to varying read, write, and execute
1208 attributes. The underlying mapped object does not change over the range of a
1209 single mapping. An \fBI/O\fR operation to a mapping marked \fBMA_SHARED\fR
1210 fails if applied at a virtual address not corresponding to a valid page in the
1211 underlying mapped object. A write to a \fBMA_SHARED\fR mapping that is not
1212 marked \fBMA_WRITE\fR fails. Reads and writes to private mappings always
1213 succeed. Reads and writes to unmapped addresses fail.
1214 .sp
1215 .LP
1216 \fBpr_pagesize\fR is the page size for the mapping, currently always the system
1217 pagesize.
1218 .sp
1219 .LP
1220 \fBpr_shmid\fR is the shared memory identifier, if any, for the mapping. Its
1221 value is \fB\(mi1\fR if the mapping is not System V shared memory. See
1222 \fBshmget\fR(2).
1223 .sp
1224 .LP
1225 \fBpr_dev\fR is the device of the mapped object, if any, for the mapping. Its
1226 value is \fBPRNODEV\fR (-1) if the mapping does not have a device.
1227 .sp
1228 .LP
1229 \fBpr_ino\fR is the inode of the mapped object, if any, for the mapping. Its
1230 contents are only valid if \fBpr_dev\fR is not \fBPRNODEV.\fR
1231 .sp
1232 .LP
1233 \fBpr_rss\fR is the number of resident pages of memory for the mapping. The
1234 number of resident bytes for the mapping may be determined by multiplying
1235 \fBpr_rss\fR by the page size given by \fBpr_pagesize.\fR
1236 .sp
1237 .LP
1238 \fBpr_anon\fR is the number of resident anonymous memory pages (pages which are
1239 private to this process) for the mapping.
1240 .sp
1241 .LP
1242 \fBpr_locked\fR is the number of locked pages for the mapping. Pages which are
1243 locked are always resident in memory.
1244 .sp
1245 .LP
1246 \fBpr_hatpagesize\fR is the size, in bytes, of the \fBHAT\fR (\fBMMU\fR)
1247 translation for the mapping. \fBpr_hatpagesize\fR may be different than
1248 \fBpr_pagesize.\fR The possible values are hardware architecture specific, and
1249 may change over a mapping's lifetime.
1250 .SS "rmap"
1251 .LP
1252 Contains information about the reserved address ranges of the process. The file
1253 contains an array of \fBprmap\fR structures, as defined above for the \fBmap\fR
1254 file. Each structure describes a contiguous virtual address region in the
1255 address space of the traced process that is reserved by the system in the sense
1256 that an \fBmmap\fR(2) system call that does not specify \fBMAP_FIXED\fR will
1257 not use any part of it for the new mapping. Examples of such reservations
1258 include the address ranges reserved for the process stack and the individual
1259 thread stacks of a multi-threaded process.
1260 .SS "cwd"
1261 .LP
1262 A symbolic link to the process's current working directory. See \fBchdir\fR(2).
1263 A \fBreadlink\fR(2) of \fB/proc/\fIpid\fR/cwd\fR yields a null string. However,
1264 it can be opened, listed, and searched as a directory, and can be the target of
1265 \fBchdir\fR(2).
1266 .SS "root"
1267 .LP
1268 A symbolic link to the process's root directory.
1269 \fB/proc/\fR\fIpid\fR\fB/root\fR can differ from the system root directory if
1270 the process or one of its ancestors executed \fBchroot\fR(2) as super user. It
1271 has the same semantics as \fB/proc/\fR\fIpid\fR\fB/cwd\fR.
1272 .SS "fd"
1273 .LP
1274 A directory containing references to the open files of the process. Each entry
1275 is a decimal number corresponding to an open file descriptor in the process.
1276 .sp
1277 .LP
1278 If an entry refers to a regular file, it can be opened with normal file system
1279 semantics but, to ensure that the controlling process cannot gain greater
1280 access than the controlled process, with no file access modes other than its
1281 read/write open modes in the controlled process. If an entry refers to a
1282 directory, it can be accessed with the same semantics as
1283 \fB/proc/\fIpid\fR/cwd\fR. An attempt to open any other type of entry fails
1284 with \fBEACCES\fR.
1285 .SS "object"
1286 .LP
1287 A directory containing read-only files with names corresponding to the
1288 \fBpr_mapname\fR entries in the \fBmap\fR and \fBpagedata\fR files. Opening
1289 such a file yields a file descriptor for the underlying mapped file associated
1290 with an address-space mapping in the process. The file name \fBa.out\fR appears
1291 in the directory as an alias for the process's executable file.
1292 .sp
1293 .LP
1294 The \fBobject\fR directory makes it possible for a controlling process to gain
1295 access to the object file and any shared libraries (and consequently the symbol
1296 tables) without having to know the actual path names of the executable files.
1297 .SS "path"
1298 .LP
1299 A directory containing symbolic links to files opened by the process. The
1300 directory includes one entry for \fBcwd\fR and \fBroot\fR. The directory also
1301 contains a numerical entry for each file descriptor in the \fBfd\fR directory,
1302 and entries matching those in the \fBobject\fR directory. If this information
1303 is not available, any attempt to read the contents of the symbolic link will
1304 fail. This is most common for files that do not exist in the filesystem
1305 namespace (such as \fBFIFO\fRs and sockets), but can also happen for regular
1306 files. For the file descriptor entries, the path may be different from the one
1307 used by the process to open the file.
1308 .SS "pagedata"
1309 .LP
1310 Opening the page data file enables tracking of address space references and
1311 modifications on a per-page basis.
1312 .sp
1313 .LP
1314 A \fBread\fR(2) of the page data file descriptor returns structured page data
1315 and atomically clears the page data maintained for the file by the system. That
1316 is to say, each read returns data collected since the last read; the first read
1317 returns data collected since the file was opened. When the call completes, the
1318 read buffer contains the following structure as its header and thereafter
1319 contains a number of section header structures and associated byte arrays that
1320 must be accessed by walking linearly through the buffer.
1321 .sp
1322 .in +2
1323 .nf
1324 typedef struct prpageheader {
1325 timestruc_t pr_tstamp; /* real time stamp, time of read() */
1326 ulong_t pr_nmap; /* number of address space mappings */
1327 ulong_t pr_npage; /* total number of pages */
1328 } prpageheader_t;
1329 .fi
1330 .in -2
1331
1332 .sp
1333 .LP
1334 The header is followed by \fBpr_nmap prasmap\fR structures and associated data
1335 arrays. The \fBprasmap\fR structure contains the following elements:
1336 .sp
1337 .in +2
1338 .nf
1339 typedef struct prasmap {
1340 uintptr_t pr_vaddr; /* virtual address of mapping */
1341 ulong_t pr_npage; /* number of pages in mapping */
1342 char pr_mapname[PRMAPSZ]; /* name in /proc/pid/object */
1343 offset_t pr_offset; /* offset into mapped object, if any */
1344 int pr_mflags; /* protection and attribute flags */
1345 int pr_pagesize; /* pagesize for this mapping in bytes */
1346 int pr_shmid; /* SysV shared memory identifier */
1347 } prasmap_t;
1348 .fi
1349 .in -2
1350
1351 .sp
1352 .LP
1353 Each section header is followed by \fBpr_npage\fR bytes, one byte for each page
1354 in the mapping, plus 0-7 null bytes at the end so that the next \fBprasmap\fR
1355 structure begins on an eight-byte aligned boundary. Each data byte may contain
1356 these flags:
1357 .sp
1358 .ne 2
1359 .na
1360 \fB\fBPG_REFERENCED\fR\fR
1361 .ad
1362 .RS 17n
1363 page has been referenced.
1364 .RE
1365
1366 .sp
1367 .ne 2
1368 .na
1369 \fB\fBPG_MODIFIED\fR\fR
1370 .ad
1371 .RS 17n
1372 page has been modified.
1373 .RE
1374
1375 .sp
1376 .LP
1377 If the read buffer is not large enough to contain all of the page data, the
1378 read fails with \fBE2BIG\fR and the page data is not cleared. The required size
1379 of the read buffer can be determined through \fBfstat\fR(2). Application of
1380 \fBlseek\fR(2) to the page data file descriptor is ineffective; every read
1381 starts from the beginning of the file. Closing the page data file descriptor
1382 terminates the system overhead associated with collecting the data.
1383 .sp
1384 .LP
1385 More than one page data file descriptor for the same process can be opened, up
1386 to a system-imposed limit per traced process. A read of one does not affect the
1387 data being collected by the system for the others. An open of the page data
1388 file will fail with \fBENOMEM\fR if the system-imposed limit would be exceeded.
1389 .SS "watch"
1390 .LP
1391 Contains an array of \fBprwatch\fR structures, one for each watched area
1392 established by the \fBPCWATCH\fR control operation. See \fBPCWATCH\fR for
1393 details.
1394 .SS "usage"
1395 .LP
1396 Contains process usage information described by a \fBprusage\fR structure which
1397 contains at least the following fields:
1398 .sp
1399 .in +2
1400 .nf
1401 typedef struct prusage {
1402 id_t pr_lwpid; /* lwp id. 0: process or defunct */
1403 int pr_count; /* number of contributing lwps */
1404 timestruc_t pr_tstamp; /* real time stamp, time of read() */
1405 timestruc_t pr_create; /* process/lwp creation time stamp */
1406 timestruc_t pr_term; /* process/lwp termination time stamp */
1407 timestruc_t pr_rtime; /* total lwp real (elapsed) time */
1408 timestruc_t pr_utime; /* user level CPU time */
1409 timestruc_t pr_stime; /* system call CPU time */
1410 timestruc_t pr_ttime; /* other system trap CPU time */
1411 timestruc_t pr_tftime; /* text page fault sleep time */
1412 timestruc_t pr_dftime; /* data page fault sleep time */
1413 timestruc_t pr_kftime; /* kernel page fault sleep time */
1414 timestruc_t pr_ltime; /* user lock wait sleep time */
1415 timestruc_t pr_slptime; /* all other sleep time */
1416 timestruc_t pr_wtime; /* wait-cpu (latency) time */
1417 timestruc_t pr_stoptime; /* stopped time */
1418 ulong_t pr_minf; /* minor page faults */
1419 ulong_t pr_majf; /* major page faults */
1420 ulong_t pr_nswap; /* swaps */
1421 ulong_t pr_inblk; /* input blocks */
1422 ulong_t pr_oublk; /* output blocks */
1423 ulong_t pr_msnd; /* messages sent */
1424 ulong_t pr_mrcv; /* messages received */
1425 ulong_t pr_sigs; /* signals received */
1426 ulong_t pr_vctx; /* voluntary context switches */
1427 ulong_t pr_ictx; /* involuntary context switches */
1428 ulong_t pr_sysc; /* system calls */
1429 ulong_t pr_ioch; /* chars read and written */
1430 } prusage_t;
1431 .fi
1432 .in -2
1433
1434 .sp
1435 .LP
1436 Microstate accounting is now continuously enabled. While this information was
1437 previously an estimate, if microstate accounting were not enabled, the current
1438 information is now never an estimate represents time the process has spent in
1439 various states.
1440 .SS "lstatus"
1441 .LP
1442 Contains a \fBprheader\fR structure followed by an array of \fBlwpstatus\fR
1443 structures, one for each active lwp in the process (see also
1444 \fB/proc/\fR\fIpid\fR\fB/lwp/\fR\fIlwpid\fR/\fBlwpstatus\fR, below). The
1445 \fBprheader\fR structure describes the number and size of the array entries
1446 that follow.
1447 .sp
1448 .in +2
1449 .nf
1450 typedef struct prheader {
1451 long pr_nent; /* number of entries */
1452 size_t pr_entsize; /* size of each entry, in bytes */
1453 } prheader_t;
1454 .fi
1455 .in -2
1456
1457 .sp
1458 .LP
1459 The \fBlwpstatus\fR structure may grow by the addition of elements at the end
1460 in future releases of the system. Programs must use \fBpr_entsize\fR in the
1461 file header to index through the array. These comments apply to all \fB/proc\fR
1462 files that include a \fBprheader\fR structure (\fBlpsinfo\fR and \fBlusage\fR,
1463 below).
1464 .SS "lpsinfo"
1465 .LP
1466 Contains a \fBprheader\fR structure followed by an array of \fBlwpsinfo\fR
1467 structures, one for eachactive and zombie lwp in the process. See also
1468 \fB/proc/\fR\fIpid\fR\fB/lwp/\fR\fIlwpid\fR/\fBlwpsinfo\fR, below.
1469 .SS "lusage"
1470 .LP
1471 Contains a \fBprheader\fR structure followed by an array of \fBprusage\fR
1472 structures, one for each active lwp in the process, plus an additional element
1473 at the beginning that contains the summation over all defunct lwps (lwps that
1474 once existed but no longer exist in the process). Excluding the \fBpr_lwpid\fR,
1475 \fBpr_tstamp\fR, \fBpr_create\fR, and \fBpr_term\fR entries, the entry-by-entry
1476 summation over all these structures is the definition of the process usage
1477 information obtained from the \fBusage\fR file. (See also
1478 \fB/proc/\fR\fIpid\fR\fB/lwp/\fR\fIlwpid\fR/\fBlwpusage\fR, below.)
1479 .SS "lwp"
1480 .LP
1481 A directory containing entries each of which names an active or zombie lwp
1482 within the process. These entries are themselves directories containing
1483 additional files as described below. Only the \fBlwpsinfo\fR file exists in the
1484 directory of a zombie lwp.
1485 .SH STRUCTURE OF \fB/proc/\fR\fIpid\fR\fB/lwp/\fR\fIlwpid\fR
1486 .LP
1487 A given directory \fB/proc/\fR\fIpid\fR\fB/lwp/\fR\fIlwpid\fR contains the
1488 following entries:
1489 .SS "lwpctl"
1490 .LP
1491 Write-only control file. The messages written to this file affect the specific
1492 lwp rather than the representative lwp, as is the case for the process's
1493 \fBctl\fR file.
1494 .SS "lwpstatus"
1495 .LP
1496 lwp-specific state information. This file contains the \fBlwpstatus\fR
1497 structure for the specific lwp as described above for the representative lwp in
1498 the process's \fBstatus\fR file.
1499 .SS "lwpsinfo"
1500 .LP
1501 lwp-specific \fBps\fR(1) information. This file contains the \fBlwpsinfo\fR
1502 structure for the specific lwp as described above for the representative lwp in
1503 the process's \fBpsinfo\fR file. The \fBlwpsinfo\fR file remains accessible
1504 after an lwp becomes a zombie.
1505 .SS "lwpusage"
1506 .LP
1507 This file contains the \fBprusage\fR structure for the specific lwp as
1508 described above for the process's \fBusage\fR file.
1509 .SS "gwindows"
1510 .LP
1511 This file exists only on SPARC based machines. If it is non-empty, it contains
1512 a \fBgwindows_t\fR structure, defined in \fB<sys/regset.h>\fR, with the values
1513 of those SPARC register windows that could not be stored on the stack when the
1514 lwp stopped. Conditions under which register windows are not stored on the
1515 stack are: the stack pointer refers to nonexistent process memory or the stack
1516 pointer is improperly aligned. If the lwp is not stopped or if there are no
1517 register windows that could not be stored on the stack, the file is empty (the
1518 usual case).
1519 .SS "xregs"
1520 .LP
1521 Extra state registers. The extra state register set is architecture dependent;
1522 this file is empty if the system does not support extra state registers. If the
1523 file is non-empty, it contains an architecture dependent structure of type
1524 \fBprxregset_t\fR, defined in \fB<procfs.h>\fR, with the values of the lwp's
1525 extra state registers. If the lwp is not stopped, all register values are
1526 undefined. See also the \fBPCSXREG\fR control operation, below.
1527 .SS "asrs"
1528 .LP
1529 This file exists only for 64-bit SPARC V9 processes. It contains an
1530 \fBasrset_t\fR structure, defined in <\fBsys/regset.h\fR>, containing the
1531 values of the lwp's platform-dependent ancillary state registers. If the lwp is
1532 not stopped, all register values are undefined. See also the \fBPCSASRS\fR
1533 control operation, below.
1534 .SS "spymaster"
1535 .LP
1536 For an agent lwp (see \fBPCAGENT\fR), this file contains a \fBpsinfo_t\fR
1537 structure that corresponds to the process that created the agent lwp at the
1538 time the agent was created. This structure is identical to that retrieved via
1539 the \fBpsinfo\fR file, with one modification: the \fBpr_time\fR field does not
1540 correspond to the CPU time for the process, but rather to the creation time of
1541 the agent lwp.
1542 .SS "templates"
1543 .LP
1544 A directory which contains references to the active templates for the lwp,
1545 named by the contract type. Changes made to an active template descriptor do
1546 not affect the original template which was activated, though they do affect the
1547 active template. It is not possible to activate an active template descriptor.
1548 See \fBcontract\fR(4).
1549 .SH CONTROL MESSAGES
1550 .LP
1551 Process state changes are effected through messages written to a process's
1552 \fBctl\fR file or to an individual lwp's \fBlwpctl\fR file. All control
1553 messages consist of a \fBlong\fR that names the specific operation followed by
1554 additional data containing the operand, if any.
1555 .sp
1556 .LP
1557 Multiple control messages may be combined in a single \fBwrite\fR(2) (or
1558 \fBwritev\fR(2)) to a control file, but no partial writes are permitted. That
1559 is, each control message, operation code plus operand, if any, must be
1560 presented in its entirety to the \fBwrite\fR(2) and not in pieces over several
1561 system calls. If a control operation fails, no subsequent operations contained
1562 in the same \fBwrite\fR(2) are attempted.
1563 .sp
1564 .LP
1565 Descriptions of the allowable control messages follow. In all cases, writing a
1566 message to a control file for a process or lwp that has terminated elicits the
1567 error \fBENOENT\fR.
1568 .SS "PCSTOP PCDSTOP PCWSTOP PCTWSTOP"
1569 .LP
1570 When applied to the process control file, \fBPCSTOP\fR directs all lwps to stop
1571 and waits for them to stop, \fBPCDSTOP\fR directs all lwps to stop without
1572 waiting for them to stop, and \fBPCWSTOP\fR simply waits for all lwps to stop.
1573 When applied to an lwp control file, \fBPCSTOP\fR directs the specific lwp to
1574 stop and waits until it has stopped, \fBPCDSTOP\fR directs the specific lwp to
1575 stop without waiting for it to stop, and \fBPCWSTOP\fR simply waits for the
1576 specific lwp to stop. When applied to an lwp control file, \fBPCSTOP\fR and
1577 \fBPCWSTOP\fR complete when the lwp stops on an event of interest, immediately
1578 if already so stopped; when applied to the process control file, they complete
1579 when every lwp has stopped either on an event of interest or on a
1580 \fBPR_SUSPENDED\fR stop.
1581 .sp
1582 .LP
1583 \fBPCTWSTOP\fR is identical to \fBPCWSTOP\fR except that it enables the
1584 operation to time out, to avoid waiting forever for a process or lwp that may
1585 never stop on an event of interest. \fBPCTWSTOP\fR takes a \fBlong\fR operand
1586 specifying a number of milliseconds; the wait will terminate successfully after
1587 the specified number of milliseconds even if the process or lwp has not
1588 stopped; a timeout value of zero makes the operation identical to
1589 \fBPCWSTOP\fR.
1590 .sp
1591 .LP
1592 An ``event of interest'' is either a \fBPR_REQUESTED\fR stop or a stop that has
1593 been specified in the process's tracing flags (set by \fBPCSTRACE\fR,
1594 \fBPCSFAULT\fR, \fBPCSENTRY\fR, and \fBPCSEXIT\fR). \fBPR_JOBCONTROL\fR and
1595 \fBPR_SUSPENDED\fR stops are specifically not events of interest. (An lwp may
1596 stop twice due to a stop signal, first showing \fBPR_SIGNALLED\fR if the signal
1597 is traced and again showing \fBPR_JOBCONTROL\fR if the lwp is set running
1598 without clearing the signal.) If \fBPCSTOP\fR or \fBPCDSTOP\fR is applied to an
1599 lwp that is stopped, but not on an event of interest, the stop directive takes
1600 effect when the lwp is restarted by the competing mechanism. At that time, the
1601 lwp enters a \fBPR_REQUESTED\fR stop before executing any user-level code.
1602 .sp
1603 .LP
1604 A write of a control message that blocks is interruptible by a signal so that,
1605 for example, an \fBalarm\fR(2) can be set to avoid waiting forever for a
1606 process or lwp that may never stop on an event of interest. If \fBPCSTOP\fR is
1607 interrupted, the lwp stop directives remain in effect even though the
1608 \fBwrite\fR(2) returns an error. (Use of \fBPCTWSTOP\fR with a non-zero timeout
1609 is recommended over \fBPCWSTOP\fR with an \fBalarm\fR(2).)
1610 .sp
1611 .LP
1612 A system process (indicated by the \fBPR_ISSYS\fR flag) never executes at user
1613 level, has no user-level address space visible through \fB/proc\fR, and cannot
1614 be stopped. Applying one of these operations to a system process or any of its
1615 lwps elicits the error \fBEBUSY\fR.
1616 .SS "PCRUN"
1617 .LP
1618 Make an lwp runnable again after a stop. This operation takes a \fBlong\fR
1619 operand containing zero or more of the following flags:
1620 .sp
1621 .ne 2
1622 .na
1623 \fB\fBPRCSIG\fR\fR
1624 .ad
1625 .RS 12n
1626 clears the current signal, if any (see \fBPCCSIG\fR).
1627 .RE
1628
1629 .sp
1630 .ne 2
1631 .na
1632 \fB\fBPRCFAULT\fR\fR
1633 .ad
1634 .RS 12n
1635 clears the current fault, if any (see \fBPCCFAULT\fR).
1636 .RE
1637
1638 .sp
1639 .ne 2
1640 .na
1641 \fB\fBPRSTEP\fR\fR
1642 .ad
1643 .RS 12n
1644 directs the lwp to execute a single machine instruction. On completion of the
1645 instruction, a trace trap occurs. If \fBFLTTRACE\fR is being traced, the lwp
1646 stops; otherwise, it is sent \fBSIGTRAP\fR. If \fBSIGTRAP\fR is being traced
1647 and is not blocked, the lwp stops. When the lwp stops on an event of interest,
1648 the single-step directive is cancelled, even if the stop occurs before the
1649 instruction is executed. This operation requires hardware and operating system
1650 support and may not be implemented on all processors. It is implemented on
1651 SPARC and x86-based machines.
1652 .RE
1653
1654 .sp
1655 .ne 2
1656 .na
1657 \fB\fBPRSABORT\fR\fR
1658 .ad
1659 .RS 12n
1660 is meaningful only if the lwp is in a \fBPR_SYSENTRY\fR stop or is marked
1661 \fBPR_ASLEEP\fR; it instructs the lwp to abort execution of the system call
1662 (see \fBPCSENTRY\fR and \fBPCSEXIT\fR).
1663 .RE
1664
1665 .sp
1666 .ne 2
1667 .na
1668 \fB\fBPRSTOP\fR\fR
1669 .ad
1670 .RS 12n
1671 directs the lwp to stop again as soon as possible after resuming execution (see
1672 \fBPCDSTOP\fR). In particular, if the lwp is stopped on \fBPR_SIGNALLED\fR or
1673 \fBPR_FAULTED\fR, the next stop will show \fBPR_REQUESTED\fR, no other stop
1674 will have intervened, and the lwp will not have executed any user-level code.
1675 .RE
1676
1677 .sp
1678 .LP
1679 When applied to an lwp control file, \fBPCRUN\fR clears any outstanding
1680 directed-stop request and makes the specific lwp runnable. The operation fails
1681 with \fBEBUSY\fR if the specific lwp is not stopped on an event of interest or
1682 has not been directed to stop or if the agent lwp exists and this is not the
1683 agent lwp (see \fBPCAGENT\fR).
1684 .sp
1685 .LP
1686 When applied to the process control file, a representative lwp is chosen for
1687 the operation as described for \fB/proc/\fR\fIpid\fR\fB/status\fR. The
1688 operation fails with \fBEBUSY\fR if the representative lwp is not stopped on an
1689 event of interest or has not been directed to stop or if the agent lwp exists.
1690 If \fBPRSTEP\fR or \fBPRSTOP\fR was requested, the representative lwp is made
1691 runnable and its outstanding directed-stop request is cleared; otherwise all
1692 outstanding directed-stop requests are cleared and, if it was stopped on an
1693 event of interest, the representative lwp is marked \fBPR_REQUESTED\fR. If, as
1694 a consequence, all lwps are in the \fBPR_REQUESTED\fR or \fBPR_SUSPENDED\fR
1695 stop state, all lwps showing \fBPR_REQUESTED\fR are made runnable.
1696 .SS "PCSTRACE"
1697 .LP
1698 Define a set of signals to be traced in the process. The receipt of one of
1699 these signals by an lwp causes the lwp to stop. The set of signals is defined
1700 using an operand \fBsigset_t\fR contained in the control message. Receipt of
1701 \fBSIGKILL\fR cannot be traced; if specified, it is silently ignored.
1702 .sp
1703 .LP
1704 If a signal that is included in an lwp's held signal set (the signal mask) is
1705 sent to the lwp, the signal is not received and does not cause a stop until it
1706 is removed from the held signal set, either by the lwp itself or by setting the
1707 held signal set with \fBPCSHOLD\fR.
1708 .SS "PCCSIG"
1709 .LP
1710 The current signal, if any, is cleared from the specific or representative lwp.
1711 .SS "PCSSIG"
1712 .LP
1713 The current signal and its associated signal information for the specific or
1714 representative lwp are set according to the contents of the operand
1715 \fBsiginfo\fR structure (see \fB<sys/siginfo.h>\fR). If the specified signal
1716 number is zero, the current signal is cleared. The semantics of this operation
1717 are different from those of \fBkill\fR(2) in that the signal is delivered to
1718 the lwp immediately after execution is resumed (even if it is being blocked)
1719 and an additional \fBPR_SIGNALLED\fR stop does not intervene even if the signal
1720 is traced. Setting the current signal to \fBSIGKILL\fR terminates the process
1721 immediately.
1722 .SS "PCKILL"
1723 .LP
1724 If applied to the process control file, a signal is sent to the process with
1725 semantics identical to those of \fBkill\fR(2). If applied to an lwp control
1726 file, a directed signal is sent to the specific lwp. The signal is named in a
1727 \fBlong\fR operand contained in the message. Sending \fBSIGKILL\fR terminates
1728 the process immediately.
1729 .SS "PCUNKILL"
1730 .LP
1731 A signal is deleted, that is, it is removed from the set of pending signals. If
1732 applied to the process control file, the signal is deleted from the process's
1733 pending signals. If applied to an lwp control file, the signal is deleted from
1734 the lwp's pending signals. The current signal (if any) is unaffected. The
1735 signal is named in a \fBlong\fR operand in the control message. It is an error
1736 (\fBEINVAL\fR) to attempt to delete \fBSIGKILL\fR.
1737 .SS "PCSHOLD"
1738 .LP
1739 Set the set of held signals for the specific or representative lwp (signals
1740 whose delivery will be blocked if sent to the lwp). The set of signals is
1741 specified with a \fBsigset_t\fR operand. \fBSIGKILL\fR and \fBSIGSTOP\fR cannot
1742 be held; if specified, they are silently ignored.
1743 .SS "PCSFAULT"
1744 .LP
1745 Define a set of hardware faults to be traced in the process. On incurring one
1746 of these faults, an lwp stops. The set is defined via the operand
1747 \fBfltset_t\fR structure. Fault names are defined in \fB<sys/fault.h>\fR and
1748 include the following. Some of these may not occur on all processors; there may
1749 be processor-specific faults in addition to these.
1750 .sp
1751 .ne 2
1752 .na
1753 \fB\fBFLTILL\fR\fR
1754 .ad
1755 .RS 13n
1756 illegal instruction
1757 .RE
1758
1759 .sp
1760 .ne 2
1761 .na
1762 \fB\fBFLTPRIV\fR\fR
1763 .ad
1764 .RS 13n
1765 privileged instruction
1766 .RE
1767
1768 .sp
1769 .ne 2
1770 .na
1771 \fB\fBFLTBPT\fR\fR
1772 .ad
1773 .RS 13n
1774 breakpoint trap
1775 .RE
1776
1777 .sp
1778 .ne 2
1779 .na
1780 \fB\fBFLTTRACE\fR\fR
1781 .ad
1782 .RS 13n
1783 trace trap (single-step)
1784 .RE
1785
1786 .sp
1787 .ne 2
1788 .na
1789 \fB\fBFLTWATCH\fR\fR
1790 .ad
1791 .RS 13n
1792 watchpoint trap
1793 .RE
1794
1795 .sp
1796 .ne 2
1797 .na
1798 \fB\fBFLTACCESS\fR\fR
1799 .ad
1800 .RS 13n
1801 memory access fault (bus error)
1802 .RE
1803
1804 .sp
1805 .ne 2
1806 .na
1807 \fB\fBFLTBOUNDS\fR\fR
1808 .ad
1809 .RS 13n
1810 memory bounds violation
1811 .RE
1812
1813 .sp
1814 .ne 2
1815 .na
1816 \fB\fBFLTIOVF\fR\fR
1817 .ad
1818 .RS 13n
1819 integer overflow
1820 .RE
1821
1822 .sp
1823 .ne 2
1824 .na
1825 \fB\fBFLTIZDIV\fR\fR
1826 .ad
1827 .RS 13n
1828 integer zero divide
1829 .RE
1830
1831 .sp
1832 .ne 2
1833 .na
1834 \fB\fBFLTFPE\fR\fR
1835 .ad
1836 .RS 13n
1837 floating-point exception
1838 .RE
1839
1840 .sp
1841 .ne 2
1842 .na
1843 \fB\fBFLTSTACK\fR\fR
1844 .ad
1845 .RS 13n
1846 unrecoverable stack fault
1847 .RE
1848
1849 .sp
1850 .ne 2
1851 .na
1852 \fB\fBFLTPAGE\fR\fR
1853 .ad
1854 .RS 13n
1855 recoverable page fault
1856 .RE
1857
1858 .sp
1859 .LP
1860 When not traced, a fault normally results in the posting of a signal to the lwp
1861 that incurred the fault. If an lwp stops on a fault, the signal is posted to
1862 the lwp when execution is resumed unless the fault is cleared by \fBPCCFAULT\fR
1863 or by the \fBPRCFAULT\fR option of \fBPCRUN\fR. \fBFLTPAGE\fR is an exception;
1864 no signal is posted. The \fBpr_info\fR field in the \fBlwpstatus\fR structure
1865 identifies the signal to be sent and contains machine-specific information
1866 about the fault.
1867 .SS "PCCFAULT"
1868 .LP
1869 The current fault, if any, is cleared; the associated signal will not be sent
1870 to the specific or representative lwp.
1871 .SS "PCSENTRY PCSEXIT"
1872 .LP
1873 These control operations instruct the process's lwps to stop on entry to or
1874 exit from specified system calls. The set of system calls to be traced is
1875 defined via an operand \fBsysset_t\fR structure.
1876 .sp
1877 .LP
1878 When entry to a system call is being traced, an lwp stops after having begun
1879 the call to the system but before the system call arguments have been fetched
1880 from the lwp. When exit from a system call is being traced, an lwp stops on
1881 completion of the system call just prior to checking for signals and returning
1882 to user level. At this point, all return values have been stored into the lwp's
1883 registers.
1884 .sp
1885 .LP
1886 If an lwp is stopped on entry to a system call (\fBPR_SYSENTRY\fR) or when
1887 sleeping in an interruptible system call (\fBPR_ASLEEP\fR is set), it may be
1888 instructed to go directly to system call exit by specifying the \fBPRSABORT\fR
1889 flag in a \fBPCRUN\fR control message. Unless exit from the system call is
1890 being traced, the lwp returns to user level showing \fBEINTR\fR.
1891 .SS "PCWATCH"
1892 .LP
1893 Set or clear a watched area in the controlled process from a \fBprwatch\fR
1894 structure operand:
1895 .sp
1896 .in +2
1897 .nf
1898 typedef struct prwatch {
1899 uintptr_t pr_vaddr; /* virtual address of watched area */
1900 size_t pr_size; /* size of watched area in bytes */
1901 int pr_wflags; /* watch type flags */
1902 } prwatch_t;
1903 .fi
1904 .in -2
1905
1906 .sp
1907 .LP
1908 \fBpr_vaddr\fR specifies the virtual address of an area of memory to be watched
1909 in the controlled process. \fBpr_size\fR specifies the size of the area, in
1910 bytes. \fBpr_wflags\fR specifies the type of memory access to be monitored as a
1911 bit-mask of the following flags:
1912 .sp
1913 .ne 2
1914 .na
1915 \fB\fBWA_READ\fR\fR
1916 .ad
1917 .RS 16n
1918 read access
1919 .RE
1920
1921 .sp
1922 .ne 2
1923 .na
1924 \fB\fBWA_WRITE\fR\fR
1925 .ad
1926 .RS 16n
1927 write access
1928 .RE
1929
1930 .sp
1931 .ne 2
1932 .na
1933 \fB\fBWA_EXEC\fR\fR
1934 .ad
1935 .RS 16n
1936 execution access
1937 .RE
1938
1939 .sp
1940 .ne 2
1941 .na
1942 \fB\fBWA_TRAPAFTER\fR\fR
1943 .ad
1944 .RS 16n
1945 trap after the instruction completes
1946 .RE
1947
1948 .sp
1949 .LP
1950 If \fBpr_wflags\fR is non-empty, a watched area is established for the virtual
1951 address range specified by \fBpr_vaddr\fR and \fBpr_size\fR. If \fBpr_wflags\fR
1952 is empty, any previously-established watched area starting at the specified
1953 virtual address is cleared; \fBpr_size\fR is ignored.
1954 .sp
1955 .LP
1956 A watchpoint is triggered when an lwp in the traced process makes a memory
1957 reference that covers at least one byte of a watched area and the memory
1958 reference is as specified in \fBpr_wflags\fR. When an lwp triggers a
1959 watchpoint, it incurs a watchpoint trap. If \fBFLTWATCH\fR is being traced, the
1960 lwp stops; otherwise, it is sent a \fBSIGTRAP\fR signal; if \fBSIGTRAP\fR is
1961 being traced and is not blocked, the lwp stops.
1962 .sp
1963 .LP
1964 The watchpoint trap occurs before the instruction completes unless
1965 \fBWA_TRAPAFTER\fR was specified, in which case it occurs after the instruction
1966 completes. If it occurs before completion, the memory is not modified. If it
1967 occurs after completion, the memory is modified (if the access is a write
1968 access).
1969 .sp
1970 .LP
1971 Physical i/o is an exception for watchpoint traps. In this instance, there is
1972 no guarantee that memory before the watched area has already been modified (or
1973 in the case of \fBWA_TRAPAFTER\fR, that the memory following the watched area
1974 has not been modified) when the watchpoint trap occurs and the lwp stops.
1975 .sp
1976 .LP
1977 \fBpr_info\fR in the \fBlwpstatus\fR structure contains information pertinent
1978 to the watchpoint trap. In particular, the \fBsi_addr\fR field contains the
1979 virtual address of the memory reference that triggered the watchpoint, and the
1980 \fBsi_code\fR field contains one of \fBTRAP_RWATCH\fR, \fBTRAP_WWATCH\fR, or
1981 \fBTRAP_XWATCH\fR, indicating read, write, or execute access, respectively. The
1982 \fBsi_trapafter\fR field is zero unless \fBWA_TRAPAFTER\fR is in effect for
1983 this watched area; non-zero indicates that the current instruction is not the
1984 instruction that incurred the watchpoint trap. The \fBsi_pc\fR field contains
1985 the virtual address of the instruction that incurred the trap.
1986 .sp
1987 .LP
1988 A watchpoint trap may be triggered while executing a system call that makes
1989 reference to the traced process's memory. The lwp that is executing the system
1990 call incurs the watchpoint trap while still in the system call. If it stops as
1991 a result, the \fBlwpstatus\fR structure contains the system call number and its
1992 arguments. If the lwp does not stop, or if it is set running again without
1993 clearing the signal or fault, the system call fails with \fBEFAULT\fR. If
1994 \fBWA_TRAPAFTER\fR was specified, the memory reference will have completed and
1995 the memory will have been modified (if the access was a write access) when the
1996 watchpoint trap occurs.
1997 .sp
1998 .LP
1999 If more than one of \fBWA_READ\fR, \fBWA_WRITE\fR, and \fBWA_EXEC\fR is
2000 specified for a watched area, and a single instruction incurs more than one of
2001 the specified types, only one is reported when the watchpoint trap occurs. The
2002 precedence is \fBWA_EXEC\fR, \fBWA_READ\fR, \fBWA_WRITE\fR (\fBWA_EXEC\fR and
2003 \fBWA_READ\fR take precedence over \fBWA_WRITE\fR), unless \fBWA_TRAPAFTER\fR
2004 was specified, in which case it is \fBWA_WRITE\fR, \fBWA_READ\fR, \fBWA_EXEC\fR
2005 (\fBWA_WRITE\fR takes precedence).
2006 .sp
2007 .LP
2008 \fBPCWATCH\fR fails with \fBEINVAL\fR if an attempt is made to specify
2009 overlapping watched areas or if \fBpr_wflags\fR contains flags other than those
2010 specified above. It fails with \fBENOMEM\fR if an attempt is made to establish
2011 more watched areas than the system can support (the system can support
2012 thousands).
2013 .sp
2014 .LP
2015 The child of a \fBvfork\fR(2) borrows the parent's address space. When a
2016 \fBvfork\fR(2) is executed by a traced process, all watched areas established
2017 for the parent are suspended until the child terminates or performs an
2018 \fBexec\fR(2). Any watched areas established independently in the child are
2019 cancelled when the parent resumes after the child's termination or
2020 \fBexec\fR(2). \fBPCWATCH\fR fails with \fBEBUSY\fR if applied to the parent of
2021 a \fBvfork\fR(2) before the child has terminated or performed an \fBexec\fR(2).
2022 The \fBPR_VFORKP\fR flag is set in the \fBpstatus\fR structure for such a
2023 parent process.
2024 .sp
2025 .LP
2026 Certain accesses of the traced process's address space by the operating system
2027 are immune to watchpoints. The initial construction of a signal stack frame
2028 when a signal is delivered to an lwp will not trigger a watchpoint trap even if
2029 the new frame covers watched areas of the stack. Once the signal handler is
2030 entered, watchpoint traps occur normally. On SPARC based machines, register
2031 window overflow and underflow will not trigger watchpoint traps, even if the
2032 register window save areas cover watched areas of the stack.
2033 .sp
2034 .LP
2035 Watched areas are not inherited by child processes, even if the traced
2036 process's inherit-on-fork mode, \fBPR_FORK\fR, is set (see \fBPCSET\fR, below).
2037 All watched areas are cancelled when the traced process performs a successful
2038 \fBexec\fR(2).
2039 .SS "PCSET PCUNSET"
2040 .LP
2041 \fBPCSET\fR sets one or more modes of operation for the traced process.
2042 \fBPCUNSET\fR unsets these modes. The modes to be set or unset are specified by
2043 flags in an operand \fBlong\fR in the control message:
2044 .sp
2045 .ne 2
2046 .na
2047 \fB\fBPR_FORK\fR\fR
2048 .ad
2049 .RS 13n
2050 (inherit-on-fork): When set, the process's tracing flags and its
2051 inherit-on-fork mode are inherited by the child of a \fBfork\fR(2),
2052 \fBfork1\fR(2), or \fBvfork\fR(2). When unset, child processes start with all
2053 tracing flags cleared.
2054 .RE
2055
2056 .sp
2057 .ne 2
2058 .na
2059 \fB\fBPR_RLC\fR\fR
2060 .ad
2061 .RS 13n
2062 (run-on-last-close): When set and the last writable \fB/proc\fR file descriptor
2063 referring to the traced process or any of its lwps is closed, all of the
2064 process's tracing flags and watched areas are cleared, any outstanding stop
2065 directives are canceled, and if any lwps are stopped on events of interest,
2066 they are set running as though \fBPCRUN\fR had been applied to them. When
2067 unset, the process's tracing flags and watched areas are retained and lwps are
2068 not set running on last close.
2069 .RE
2070
2071 .sp
2072 .ne 2
2073 .na
2074 \fB\fBPR_KLC\fR\fR
2075 .ad
2076 .RS 13n
2077 (kill-on-last-close): When set and the last writable \fB/proc\fR file
2078 descriptor referring to the traced process or any of its lwps is closed, the
2079 process is terminated with \fBSIGKILL\fR.
2080 .RE
2081
2082 .sp
2083 .ne 2
2084 .na
2085 \fB\fBPR_ASYNC\fR\fR
2086 .ad
2087 .RS 13n
2088 (asynchronous-stop): When set, a stop on an event of interest by one lwp does
2089 not directly affect any other lwp in the process. When unset and an lwp stops
2090 on an event of interest other than \fBPR_REQUESTED\fR, all other lwps in the
2091 process are directed to stop.
2092 .RE
2093
2094 .sp
2095 .ne 2
2096 .na
2097 \fB\fBPR_MSACCT\fR\fR
2098 .ad
2099 .RS 13n
2100 (microstate accounting): Microstate accounting is now continuously enabled.
2101 This flag is deprecated and no longer has any effect upon microstate
2102 accounting. Applications may toggle this flag; however, microstate accounting
2103 will remain enabled regardless.
2104 .RE
2105
2106 .sp
2107 .ne 2
2108 .na
2109 \fB\fBPR_MSFORK\fR\fR
2110 .ad
2111 .RS 13n
2112 (inherit microstate accounting): All processes now inherit microstate
2113 accounting, as it is continuously enabled. This flag has been deprecated and
2114 its use no longer has any effect upon the behavior of microstate accounting.
2115 .RE
2116
2117 .sp
2118 .ne 2
2119 .na
2120 \fB\fBPR_BPTADJ\fR\fR
2121 .ad
2122 .RS 13n
2123 (breakpoint trap pc adjustment): On x86-based machines, a breakpoint trap
2124 leaves the program counter (the \fBEIP\fR) referring to the breakpointed
2125 instruction plus one byte. When \fBPR_BPTADJ\fR is set, the system will adjust
2126 the program counter back to the location of the breakpointed instruction when
2127 the lwp stops on a breakpoint. This flag has no effect on SPARC based machines,
2128 where breakpoint traps leave the program counter referring to the breakpointed
2129 instruction.
2130 .RE
2131
2132 .sp
2133 .ne 2
2134 .na
2135 \fB\fBPR_PTRACE\fR\fR
2136 .ad
2137 .RS 13n
2138 (ptrace-compatibility): When set, a stop on an event of interest by the traced
2139 process is reported to the parent of the traced process by \fBwait\fR(3C),
2140 \fBSIGTRAP\fR is sent to the traced process when it executes a successful
2141 \fBexec\fR(2), setuid/setgid flags are not honored for execs performed by the
2142 traced process, any exec of an object file that the traced process cannot read
2143 fails, and the process dies when its parent dies. This mode is deprecated; it
2144 is provided only to allow \fBptrace\fR(3C) to be implemented as a library
2145 function using \fB/proc\fR.
2146 .RE
2147
2148 .sp
2149 .LP
2150 It is an error (\fBEINVAL\fR) to specify flags other than those described above
2151 or to apply these operations to a system process. The current modes are
2152 reported in the \fBpr_flags\fR field of \fB/proc/\fR\fIpid\fR\fB/status\fR and
2153 \fB/proc/\fR\fIpid\fR\fB/lwp/\fR\fIlwp\fR\fB/lwpstatus\fR.
2154 .SS "PCSREG"
2155 .LP
2156 Set the general registers for the specific or representative lwp according to
2157 the operand \fBprgregset_t\fR structure.
2158 .sp
2159 .LP
2160 On SPARC based systems, only the condition-code bits of the processor-status
2161 register (R_PSR) of SPARC V8 (32-bit) processes can be modified by
2162 \fBPCSREG\fR. Other privileged registers cannot be modified at all.
2163 .sp
2164 .LP
2165 On x86-based systems, only certain bits of the flags register (EFL) can be
2166 modified by \fBPCSREG\fR: these include the condition codes, direction-bit, and
2167 overflow-bit.
2168 .sp
2169 .LP
2170 \fBPCSREG\fR fails with \fBEBUSY\fR if the lwp is not stopped on an event of
2171 interest.
2172 .SS "PCSVADDR"
2173 .LP
2174 Set the address at which execution will resume for the specific or
2175 representative lwp from the operand \fBlong\fR. On SPARC based systems, both
2176 %pc and %npc are set, with %npc set to the instruction following the virtual
2177 address. On x86-based systems, only %eip is set. \fBPCSVADDR\fR fails with
2178 \fBEBUSY\fR if the lwp is not stopped on an event of interest.
2179 .SS "PCSFPREG"
2180 .LP
2181 Set the floating-point registers for the specific or representative lwp
2182 according to the operand \fBprfpregset_t\fR structure. An error (\fBEINVAL\fR)
2183 is returned if the system does not support floating-point operations (no
2184 floating-point hardware and the system does not emulate floating-point machine
2185 instructions). \fBPCSFPREG\fR fails with \fBEBUSY\fR if the lwp is not stopped
2186 on an event of interest.
2187 .SS "PCSXREG"
2188 .LP
2189 Set the extra state registers for the specific or representative lwp according
2190 to the architecture-dependent operand \fBprxregset_t\fR structure. An error
2191 (\fBEINVAL\fR) is returned if the system does not support extra state
2192 registers. \fBPCSXREG\fR fails with \fBEBUSY\fR if the lwp is not stopped on an
2193 event of interest.
2194 .SS "PCSASRS"
2195 .LP
2196 Set the ancillary state registers for the specific or representative lwp
2197 according to the SPARC V9 platform-dependent operand \fBasrset_t\fR structure.
2198 An error (\fBEINVAL\fR) is returned if either the target process or the
2199 controlling process is not a 64-bit SPARC V9 process. Most of the ancillary
2200 state registers are privileged registers that cannot be modified. Only those
2201 that can be modified are set; all others are silently ignored. \fBPCSASRS\fR
2202 fails with \fBEBUSY\fR if the lwp is not stopped on an event of interest.
2203 .SS "PCAGENT"
2204 .LP
2205 Create an agent lwp in the controlled process with register values from the
2206 operand \fBprgregset_t\fR structure (see \fBPCSREG\fR, above). The agent lwp is
2207 created in the stopped state showing \fBPR_REQUESTED\fR and with its held
2208 signal set (the signal mask) having all signals except \fBSIGKILL\fR and
2209 \fBSIGSTOP\fR blocked.
2210 .sp
2211 .LP
2212 The \fBPCAGENT\fR operation fails with \fBEBUSY\fR unless the process is fully
2213 stopped via \fB/proc\fR, that is, unless all of the lwps in the process are
2214 stopped either on events of interest or on \fBPR_SUSPENDED\fR, or are stopped
2215 on \fBPR_JOBCONTROL\fR and have been directed to stop via \fBPCDSTOP\fR. It
2216 fails with \fBEBUSY\fR if an agent lwp already exists. It fails with
2217 \fBENOMEM\fR if system resources for creating new lwps have been exhausted.
2218 .sp
2219 .LP
2220 Any \fBPCRUN\fR operation applied to the process control file or to the control
2221 file of an lwp other than the agent lwp fails with \fBEBUSY\fR as long as the
2222 agent lwp exists. The agent lwp must be caused to terminate by executing the
2223 \fBSYS_lwp_exit\fR system call trap before the process can be restarted.
2224 .sp
2225 .LP
2226 Once the agent lwp is created, its lwp-ID can be found by reading the process
2227 status file. To facilitate opening the agent lwp's control and status files,
2228 the directory name \fB/propc/\fR\fIpid\fR\fB/lwp/agent\fR is accepted for
2229 lookup operations as an invisible alias for
2230 \fB/proc/\fR\fIpid\fR\fB/lwp/\fR\fIlwpid,\fR \fIlwpid\fR being the lwp-ID of
2231 the agent lwp (invisible in the sense that the name ``agent'' does not appear
2232 in a directory listing of \fB/proc/\fR\fIpid\fR\fB/lwp\fR obtained from
2233 \fBls\fR(1), \fBgetdents\fR(2), or \fBreaddir\fR(3C)).
2234 .sp
2235 .LP
2236 The purpose of the agent lwp is to perform operations in the controlled process
2237 on behalf of the controlling process: to gather information not directly
2238 available via \fB/proc\fR files, or in general to make the process change state
2239 in ways not directly available via \fB/proc\fR control operations. To make use
2240 of an agent lwp, the controlling process must be capable of making it execute
2241 system calls (specifically, the \fBSYS_lwp_exit\fR system call trap). The
2242 register values given to the agent lwp on creation are typically the registers
2243 of the representative lwp, so that the agent lwp can use its stack.
2244 .sp
2245 .LP
2246 If the controlling process neglects to force the agent lwp to execute the
2247 \fBSYS_lwp_exit\fR system call (due to either logic error or fatal failure on
2248 the part of the controlling process), the agent lwp will remain in the target
2249 process. For purposes of being able to debug these otherwise rogue agents,
2250 information as to the creator of the agent lwp is reflected in that lwp's
2251 \fBspymaster\fR file in \fB/proc\fR. Should the target process generate a core
2252 dump with the agent lwp in place, this information will be available via the
2253 \fBNT_SPYMASTER\fR note in the core file (see \fBcore\fR(4)).
2254 .sp
2255 .LP
2256 The agent lwp is not allowed to execute any variation of the \fBSYS_fork\fR or
2257 \fBSYS_exec\fR system call traps. Attempts to do so yield \fBENOTSUP\fR to the
2258 agent lwp.
2259 .sp
2260 .LP
2261 Symbolic constants for system call trap numbers like \fBSYS_lwp_exit\fR and
2262 \fBSYS_lwp_create\fR can be found in the header file <\fBsys/syscall.h\fR>.
2263 .SS "PCREAD PCWRITE"
2264 .LP
2265 Read or write the target process's address space via a \fBpriovec\fR structure
2266 operand:
2267 .sp
2268 .in +2
2269 .nf
2270 typedef struct priovec {
2271 void *pio_base; /* buffer in controlling process */
2272 size_t pio_len; /* size of read/write request in bytes */
2273 off_t pio_offset; /* virtual address in target process */
2274 } priovec_t;
2275 .fi
2276 .in -2
2277
2278 .sp
2279 .LP
2280 These operations have the same effect as \fBpread\fR(2) and \fBpwrite\fR(2),
2281 respectively, of the target process's address space file. The difference is
2282 that more than one \fBPCREAD\fR or \fBPCWRITE\fR control operation can be
2283 written to the control file at once, and they can be interspersed with other
2284 control operations in a single write to the control file. This is useful, for
2285 example, when planting many breakpoint instructions in the process's address
2286 space, or when stepping over a breakpointed instruction. Unlike \fBpread\fR(2)
2287 and \fBpwrite\fR(2), no provision is made for partial reads or writes; if the
2288 operation cannot be performed completely, it fails with \fBEIO\fR.
2289 .SS "PCNICE"
2290 .LP
2291 The traced process's \fBnice\fR(2) value is incremented by the amount in the
2292 operand \fBlong\fR. Only a process with the {\fBPRIV_PROC_PRIOCNTL\fR}
2293 privilege asserted in its effective set can better a process's priority in this
2294 way, but any user may lower the priority. This operation is not meaningful for
2295 all scheduling classes.
2296 .SS "PCSCRED"
2297 .LP
2298 Set the target process credentials to the values contained in the
2299 \fBprcred_t\fR structure operand (see \fB/proc/\fR\fIpid\fR\fB/cred\fR). The
2300 effective, real, and saved user-IDs and group-IDs of the target process are
2301 set. The target process's supplementary groups are not changed; the
2302 \fBpr_ngroups\fR and \fBpr_groups\fR members of the structure operand are
2303 ignored. Only the privileged processes can perform this operation; for all
2304 others it fails with \fBEPERM\fR.
2305 .SS "PCSCREDX"
2306 .LP
2307 Operates like \fBPCSCRED\fR but also sets the supplementary groups; the length
2308 of the data written with this control operation should be "sizeof
2309 (\fBprcred_t\fR) + sizeof (\fBgid_t)\fR * (#groups - 1)".
2310 .SS "PCSPRIV"
2311 .LP
2312 Set the target process privilege to the values contained in the \fBprpriv_t\fR
2313 operand (see \fB/proc/pid/priv\fR). The effective, permitted, inheritable, and
2314 limit sets are all changed. Privilege flags can also be set. The process is
2315 made privilege aware unless it can relinquish privilege awareness. See
2316 \fBprivileges\fR(5).
2317 .sp
2318 .LP
2319 The limit set of the target process cannot be grown. The other privilege sets
2320 must be subsets of the intersection of the effective set of the calling process
2321 with the new limit set of the target process or subsets of the original values
2322 of the sets in the target process.
2323 .sp
2324 .LP
2325 If any of the above restrictions are not met, \fBEPERM\fR is returned. If the
2326 structure written is improperly formatted, \fBEINVAL\fR is returned.
2327 .SH PROGRAMMING NOTES
2328 .LP
2329 For security reasons, except for the \fBpsinfo\fR, \fBusage\fR, \fBlpsinfo\fR,
2330 \fBlusage\fR, \fBlwpsinfo\fR, and \fBlwpusage\fR files, which are
2331 world-readable, and except for privileged processes, an open of a \fB/proc\fR
2332 file fails unless both the user-ID and group-ID of the caller match those of
2333 the traced process and the process's object file is readable by the caller. The
2334 effective set of the caller is a superset of both the inheritable and the
2335 permitted set of the target process. The limit set of the caller is a superset
2336 of the limit set of the target process. Except for the world-readable files
2337 just mentioned, files corresponding to setuid and setgid processes can be
2338 opened only by the appropriately privileged process.
2339 .sp
2340 .LP
2341 A process that is missing the basic privilege {\fBPRIV_PROC_INFO\fR} cannot see
2342 any processes under \fB/proc\fR that it cannot send a signal to.
2343 .sp
2344 .LP
2345 A process that has {\fBPRIV_PROC_OWNER\fR} asserted in its effective set can
2346 open any file for reading. To manipulate or control a process, the controlling
2347 process must have at least as many privileges in its effective set as the
2348 target process has in its effective, inheritable, and permitted sets. The limit
2349 set of the controlling process must be a superset of the limit set of the
2350 target process. Additional restrictions apply if any of the uids of the target
2351 process are 0. See \fBprivileges\fR(5).
2352 .sp
2353 .LP
2354 Even if held by a privileged process, an open process or lwp file descriptor
2355 (other than file descriptors for the world-readable files) becomes invalid if
2356 the traced process performs an \fBexec\fR(2) of a setuid/setgid object file or
2357 an object file that the traced process cannot read. Any operation performed on
2358 an invalid file descriptor, except \fBclose\fR(2), fails with \fBEAGAIN\fR. In
2359 this situation, if any tracing flags are set and the process or any lwp file
2360 descriptor is open for writing, the process will have been directed to stop and
2361 its run-on-last-close flag will have been set (see \fBPCSET\fR). This enables a
2362 controlling process (if it has permission) to reopen the \fB/proc\fR files to
2363 get new valid file descriptors, close the invalid file descriptors, unset the
2364 run-on-last-close flag (if desired), and proceed. Just closing the invalid file
2365 descriptors causes the traced process to resume execution with all tracing
2366 flags cleared. Any process not currently open for writing via \fB/proc\fR, but
2367 that has left-over tracing flags from a previous open, and that executes a
2368 setuid/setgid or unreadable object file, will not be stopped but will have all
2369 its tracing flags cleared.
2370 .sp
2371 .LP
2372 To wait for one or more of a set of processes or lwps to stop or terminate,
2373 \fB/proc\fR file descriptors (other than those obtained by opening the
2374 \fBcwd\fR or \fBroot\fR directories or by opening files in the \fBfd\fR or
2375 \fBobject\fR directories) can be used in a \fBpoll\fR(2) system call. When
2376 requested and returned, either of the polling events \fBPOLLPRI\fR or
2377 \fBPOLLWRNORM\fR indicates that the process or lwp stopped on an event of
2378 interest. Although they cannot be requested, the polling events \fBPOLLHUP\fR,
2379 \fBPOLLERR\fR, and \fBPOLLNVAL\fR may be returned. \fBPOLLHUP\fR indicates that
2380 the process or lwp has terminated. \fBPOLLERR\fR indicates that the file
2381 descriptor has become invalid. \fBPOLLNVAL\fR is returned immediately if
2382 \fBPOLLPRI\fR or \fBPOLLWRNORM\fR is requested on a file descriptor referring
2383 to a system process (see \fBPCSTOP\fR). The requested events may be empty to
2384 wait simply for termination.
2385 .SH FILES
2386 .ne 2
2387 .na
2388 \fB\fB/proc\fR\fR
2389 .ad
2390 .sp .6
2391 .RS 4n
2392 directory (list of processes)
2393 .RE
2394
2395 .sp
2396 .ne 2
2397 .na
2398 \fB\fB/proc/\fIpid\fR\fR\fR
2399 .ad
2400 .sp .6
2401 .RS 4n
2402 specific process directory
2403 .RE
2404
2405 .sp
2406 .ne 2
2407 .na
2408 \fB\fB/proc/self\fR\fR
2409 .ad
2410 .sp .6
2411 .RS 4n
2412 alias for a process's own directory
2413 .RE
2414
2415 .sp
2416 .ne 2
2417 .na
2418 \fB\fB/proc/\fIpid\fR/as\fR\fR
2419 .ad
2420 .sp .6
2421 .RS 4n
2422 address space file
2423 .RE
2424
2425 .sp
2426 .ne 2
2427 .na
2428 \fB\fB/proc/\fIpid\fR/ctl\fR\fR
2429 .ad
2430 .sp .6
2431 .RS 4n
2432 process control file
2433 .RE
2434
2435 .sp
2436 .ne 2
2437 .na
2438 \fB\fB/proc/\fIpid\fR/status\fR\fR
2439 .ad
2440 .sp .6
2441 .RS 4n
2442 process status
2443 .RE
2444
2445 .sp
2446 .ne 2
2447 .na
2448 \fB\fB/proc/\fIpid\fR/lstatus\fR\fR
2449 .ad
2450 .sp .6
2451 .RS 4n
2452 array of lwp status structs
2453 .RE
2454
2455 .sp
2456 .ne 2
2457 .na
2458 \fB\fB/proc/\fIpid\fR/psinfo\fR\fR
2459 .ad
2460 .sp .6
2461 .RS 4n
2462 process \fBps\fR(1) info
2463 .RE
2464
2465 .sp
2466 .ne 2
2467 .na
2468 \fB\fB/proc/\fIpid\fR/lpsinfo\fR\fR
2469 .ad
2470 .sp .6
2471 .RS 4n
2472 array of lwp \fBps\fR(1) info structs
2473 .RE
2474
2475 .sp
2476 .ne 2
2477 .na
2478 \fB\fB/proc/\fIpid\fR/map\fR\fR
2479 .ad
2480 .sp .6
2481 .RS 4n
2482 address space map
2483 .RE
2484
2485 .sp
2486 .ne 2
2487 .na
2488 \fB\fB/proc/\fIpid\fR/xmap\fR\fR
2489 .ad
2490 .sp .6
2491 .RS 4n
2492 extended address space map
2493 .RE
2494
2495 .sp
2496 .ne 2
2497 .na
2498 \fB\fB/proc/\fIpid\fR/rmap\fR\fR
2499 .ad
2500 .sp .6
2501 .RS 4n
2502 reserved address map
2503 .RE
2504
2505 .sp
2506 .ne 2
2507 .na
2508 \fB\fB/proc/\fIpid\fR/cred\fR\fR
2509 .ad
2510 .sp .6
2511 .RS 4n
2512 process credentials
2513 .RE
2514
2515 .sp
2516 .ne 2
2517 .na
2518 \fB\fB/proc/\fIpid\fR/priv\fR\fR
2519 .ad
2520 .sp .6
2521 .RS 4n
2522 process privileges
2523 .RE
2524
2525 .sp
2526 .ne 2
2527 .na
2528 \fB\fB/proc/\fIpid\fR/sigact\fR\fR
2529 .ad
2530 .sp .6
2531 .RS 4n
2532 process signal actions
2533 .RE
2534
2535 .sp
2536 .ne 2
2537 .na
2538 \fB\fB/proc/\fIpid\fR/auxv\fR\fR
2539 .ad
2540 .sp .6
2541 .RS 4n
2542 process aux vector
2543 .RE
2544
2545 .sp
2546 .ne 2
2547 .na
2548 \fB\fB/proc/\fIpid\fR/argv\fR\fR
2549 .ad
2550 .sp .6
2551 .RS 4n
2552 process argument vector
2553 .RE
2554
2555 .sp
2556 .ne 2
2557 .na
2558 \fB\fB/proc/\fIpid\fR/ldt\fR\fR
2559 .ad
2560 .sp .6
2561 .RS 4n
2562 process \fBLDT\fR (x86 only)
2563 .RE
2564
2565 .sp
2566 .ne 2
2567 .na
2568 \fB\fB/proc/\fIpid\fR/usage\fR\fR
2569 .ad
2570 .sp .6
2571 .RS 4n
2572 process usage
2573 .RE
2574
2575 .sp
2576 .ne 2
2577 .na
2578 \fB\fB/proc/\fIpid\fR/lusage\fR\fR
2579 .ad
2580 .sp .6
2581 .RS 4n
2582 array of lwp usage structs
2583 .RE
2584
2585 .sp
2586 .ne 2
2587 .na
2588 \fB\fB/proc/\fIpid\fR/path\fR\fR
2589 .ad
2590 .sp .6
2591 .RS 4n
2592 symbolic links to process open files
2593 .RE
2594
2595 .sp
2596 .ne 2
2597 .na
2598 \fB\fB/proc/\fIpid\fR/pagedata\fR\fR
2599 .ad
2600 .sp .6
2601 .RS 4n
2602 process page data
2603 .RE
2604
2605 .sp
2606 .ne 2
2607 .na
2608 \fB\fB/proc/\fIpid\fR/watch\fR\fR
2609 .ad
2610 .sp .6
2611 .RS 4n
2612 active watchpoints
2613 .RE
2614
2615 .sp
2616 .ne 2
2617 .na
2618 \fB\fB/proc/\fIpid\fR/cwd\fR\fR
2619 .ad
2620 .sp .6
2621 .RS 4n
2622 alias for the current working directory
2623 .RE
2624
2625 .sp
2626 .ne 2
2627 .na
2628 \fB\fB/proc/\fIpid\fR/root\fR\fR
2629 .ad
2630 .sp .6
2631 .RS 4n
2632 alias for the root directory
2633 .RE
2634
2635 .sp
2636 .ne 2
2637 .na
2638 \fB\fB/proc/\fIpid\fR/fd\fR\fR
2639 .ad
2640 .sp .6
2641 .RS 4n
2642 directory (list of open files)
2643 .RE
2644
2645 .sp
2646 .ne 2
2647 .na
2648 \fB\fB/proc/\fIpid\fR/fd/*\fR\fR
2649 .ad
2650 .sp .6
2651 .RS 4n
2652 aliases for process's open files
2653 .RE
2654
2655 .sp
2656 .ne 2
2657 .na
2658 \fB\fB/proc/\fIpid\fR/object\fR\fR
2659 .ad
2660 .sp .6
2661 .RS 4n
2662 directory (list of mapped files)
2663 .RE
2664
2665 .sp
2666 .ne 2
2667 .na
2668 \fB\fB/proc/\fIpid\fR/object/a.out\fR\fR
2669 .ad
2670 .sp .6
2671 .RS 4n
2672 alias for process's executable file
2673 .RE
2674
2675 .sp
2676 .ne 2
2677 .na
2678 \fB\fB/proc/\fIpid\fR/object/*\fR\fR
2679 .ad
2680 .sp .6
2681 .RS 4n
2682 aliases for other mapped files
2683 .RE
2684
2685 .sp
2686 .ne 2
2687 .na
2688 \fB\fB/proc/\fIpid\fR/lwp\fR\fR
2689 .ad
2690 .sp .6
2691 .RS 4n
2692 directory (list of lwps)
2693 .RE
2694
2695 .sp
2696 .ne 2
2697 .na
2698 \fB\fB/proc/\fIpid\fR/lwp/\fIlwpid\fR\fR\fR
2699 .ad
2700 .sp .6
2701 .RS 4n
2702 specific lwp directory
2703 .RE
2704
2705 .sp
2706 .ne 2
2707 .na
2708 \fB\fB/proc/\fIpid\fR/lwp/agent\fR\fR
2709 .ad
2710 .sp .6
2711 .RS 4n
2712 alias for the agent lwp directory
2713 .RE
2714
2715 .sp
2716 .ne 2
2717 .na
2718 \fB\fB/proc/\fIpid\fR/lwp/\fIlwpid\fR/lwpctl\fR\fR
2719 .ad
2720 .sp .6
2721 .RS 4n
2722 lwp control file
2723 .RE
2724
2725 .sp
2726 .ne 2
2727 .na
2728 \fB\fB/proc/\fIpid\fR/lwp/\fIlwpid\fR/lwpstatus\fR\fR
2729 .ad
2730 .sp .6
2731 .RS 4n
2732 lwp status
2733 .RE
2734
2735 .sp
2736 .ne 2
2737 .na
2738 \fB\fB/proc/\fIpid\fR/lwp/\fIlwpid\fR/lwpsinfo\fR\fR
2739 .ad
2740 .sp .6
2741 .RS 4n
2742 lwp \fBps\fR(1) info
2743 .RE
2744
2745 .sp
2746 .ne 2
2747 .na
2748 \fB\fB/proc/\fIpid\fR/lwp/\fIlwpid\fR/lwpusage\fR\fR
2749 .ad
2750 .sp .6
2751 .RS 4n
2752 lwp usage
2753 .RE
2754
2755 .sp
2756 .ne 2
2757 .na
2758 \fB\fB/proc/\fIpid\fR/lwp/\fIlwpid\fR/gwindows\fR\fR
2759 .ad
2760 .sp .6
2761 .RS 4n
2762 register windows (SPARC only)
2763 .RE
2764
2765 .sp
2766 .ne 2
2767 .na
2768 \fB\fB/proc/\fIpid\fR/lwp/\fIlwpid\fR/xregs\fR\fR
2769 .ad
2770 .sp .6
2771 .RS 4n
2772 extra state registers
2773 .RE
2774
2775 .sp
2776 .ne 2
2777 .na
2778 \fB\fB/proc/\fIpid\fR/lwp/\fIlwpid\fR/asrs\fR\fR
2779 .ad
2780 .sp .6
2781 .RS 4n
2782 ancillary state registers (SPARC V9 only)
2783 .RE
2784
2785 .sp
2786 .ne 2
2787 .na
2788 \fB\fB/proc/\fIpid\fR/lwp/\fIlwpid\fR/spymaster\fR\fR
2789 .ad
2790 .sp .6
2791 .RS 4n
2792 For an agent LWP, the controlling process
2793 .RE
2794
2795 .SH SEE ALSO
2796 .LP
2797 \fBls\fR(1), \fBps\fR(1), \fBchroot\fR(1M), \fBalarm\fR(2), \fBbrk\fR(2),
2798 \fBchdir\fR(2), \fBchroot\fR(2), \fBclose\fR(2), \fBcreat\fR(2), \fBdup\fR(2),
2799 \fBexec\fR(2), \fBfcntl\fR(2), \fBfork\fR(2), \fBfork1\fR(2), \fBfstat\fR(2),
2800 \fBgetdents\fR(2), \fBgetustack\fR(2), \fBkill\fR(2), \fBlseek\fR(2),
2801 \fBmmap\fR(2), \fBnice\fR(2), \fBopen\fR(2), \fBpoll\fR(2), \fBpread\fR(2),
2802 \fBptrace\fR(3C), \fBpwrite\fR(2), \fBread\fR(2), \fBreadlink\fR(2),
2803 \fBreadv\fR(2), \fBshmget\fR(2), \fBsigaction\fR(2), \fBsigaltstack\fR(2),
2804 \fBvfork\fR(2), \fBwrite\fR(2), \fBwritev\fR(2), \fB_stack_grow\fR(3C),
2805 \fBreaddir\fR(3C), \fBpthread_create\fR(3C), \fBpthread_join\fR(3C),
2806 \fBsiginfo.h\fR(3HEAD), \fBsignal.h\fR(3HEAD), \fBthr_create\fR(3C),
2807 \fBthr_join\fR(3C), \fBtypes32.h\fR(3HEAD), \fBucontext.h\fR(3HEAD),
2808 \fBwait\fR(3C), \fBcontract\fR(4), \fBcore\fR(4), \fBprocess\fR(4),
2809 \fBlfcompile\fR(5), \fBprivileges\fR(5)
2810 .SH DIAGNOSTICS
2811 .LP
2812 Errors that can occur in addition to the errors normally associated with file
2813 system access:
2814 .sp
2815 .ne 2
2816 .na
2817 \fB\fBE2BIG\fR\fR
2818 .ad
2819 .RS 13n
2820 Data to be returned in a \fBread\fR(2) of the page data file exceeds the size
2821 of the read buffer provided by the caller.
2822 .RE
2823
2824 .sp
2825 .ne 2
2826 .na
2827 \fB\fBEACCES\fR\fR
2828 .ad
2829 .RS 13n
2830 An attempt was made to examine a process that ran under a different uid than
2831 the controlling process and {\fBPRIV_PROC_OWNER\fR} was not asserted in the
2832 effective set.
2833 .RE
2834
2835 .sp
2836 .ne 2
2837 .na
2838 \fB\fBEAGAIN\fR\fR
2839 .ad
2840 .RS 13n
2841 The traced process has performed an \fBexec\fR(2) of a setuid/setgid object
2842 file or of an object file that it cannot read; all further operations on the
2843 process or lwp file descriptor (except \fBclose\fR(2)) elicit this error.
2844 .RE
2845
2846 .sp
2847 .ne 2
2848 .na
2849 \fB\fBEBUSY\fR\fR
2850 .ad
2851 .RS 13n
2852 \fBPCSTOP\fR, \fBPCDSTOP\fR, \fBPCWSTOP\fR, or \fBPCTWSTOP\fR was applied to a
2853 system process; an exclusive \fBopen\fR(2) was attempted on a \fB/proc\fR file
2854 for a process already open for writing; \fBPCRUN\fR, \fBPCSREG\fR,
2855 \fBPCSVADDR\fR, \fBPCSFPREG\fR, or \fBPCSXREG\fR was applied to a process or
2856 lwp not stopped on an event of interest; an attempt was made to mount
2857 \fB/proc\fR when it was already mounted; \fBPCAGENT\fR was applied to a process
2858 that was not fully stopped or that already had an agent lwp.
2859 .RE
2860
2861 .sp
2862 .ne 2
2863 .na
2864 \fB\fBEINVAL\fR\fR
2865 .ad
2866 .RS 13n
2867 In general, this means that some invalid argument was supplied to a system
2868 call. A non-exhaustive list of conditions eliciting this error includes: a
2869 control message operation code is undefined; an out-of-range signal number was
2870 specified with \fBPCSSIG\fR, \fBPCKILL\fR, or \fBPCUNKILL\fR; \fBSIGKILL\fR was
2871 specified with \fBPCUNKILL\fR; \fBPCSFPREG\fR was applied on a system that does
2872 not support floating-point operations; \fBPCSXREG\fR was applied on a system
2873 that does not support extra state registers.
2874 .RE
2875
2876 .sp
2877 .ne 2
2878 .na
2879 \fB\fBEINTR\fR\fR
2880 .ad
2881 .RS 13n
2882 A signal was received by the controlling process while waiting for the traced
2883 process or lwp to stop via \fBPCSTOP\fR, \fBPCWSTOP\fR, or \fBPCTWSTOP\fR.
2884 .RE
2885
2886 .sp
2887 .ne 2
2888 .na
2889 \fB\fBEIO\fR\fR
2890 .ad
2891 .RS 13n
2892 A \fBwrite\fR(2) was attempted at an illegal address in the traced process.
2893 .RE
2894
2895 .sp
2896 .ne 2
2897 .na
2898 \fB\fBENOENT\fR\fR
2899 .ad
2900 .RS 13n
2901 The traced process or lwp has terminated after being opened. The basic
2902 privilege {\fBPRIV_PROC_INFO\fR} is not asserted in the effective set of the
2903 calling process and the calling process cannot send a signal to the target
2904 process.
2905 .RE
2906
2907 .sp
2908 .ne 2
2909 .na
2910 \fB\fBENOMEM\fR\fR
2911 .ad
2912 .RS 13n
2913 The system-imposed limit on the number of page data file descriptors was
2914 reached on an open of \fB/proc/\fR\fIpid\fR\fB/pagedata\fR; an attempt was made
2915 with \fBPCWATCH\fR to establish more watched areas than the system can support;
2916 the \fBPCAGENT\fR operation was issued when the system was out of resources for
2917 creating lwps.
2918 .RE
2919
2920 .sp
2921 .ne 2
2922 .na
2923 \fB\fBENOSYS\fR\fR
2924 .ad
2925 .RS 13n
2926 An attempt was made to perform an unsupported operation (such as
2927 \fBcreat\fR(2), \fBlink\fR(2), or \fBunlink\fR(2)) on an entry in \fB/proc\fR.
2928 .RE
2929
2930 .sp
2931 .ne 2
2932 .na
2933 \fB\fBEOVERFLOW\fR\fR
2934 .ad
2935 .RS 13n
2936 A 32-bit controlling process attempted to read or write the \fBas\fR file or
2937 attempted to read the \fBmap\fR, \fBrmap\fR, or \fBpagedata\fR file of a 64-bit
2938 target process. A 32-bit controlling process attempted to apply one of the
2939 control operations \fBPCSREG\fR, \fBPCSXREG\fR, \fBPCSVADDR\fR, \fBPCWATCH\fR,
2940 \fBPCAGENT\fR, \fBPCREAD\fR, \fBPCWRITE\fR to a 64-bit target process.
2941 .RE
2942
2943 .sp
2944 .ne 2
2945 .na
2946 \fB\fBEPERM\fR\fR
2947 .ad
2948 .RS 13n
2949 The process that issued the \fBPCSCRED\fR or \fBPCSCREDX\fR operation did not
2950 have the {\fBPRIV_PROC_SETID\fR} privilege asserted in its effective set, or
2951 the process that issued the \fBPCNICE\fR operation did not have the
2952 {\fBPRIV_PROC_PRIOCNTL\fR} in its effective set.
2953 .sp
2954 An attempt was made to control a process of which the E, P, and I privilege
2955 sets were not a subset of the effective set of the controlling process or the
2956 limit set of the controlling process is not a superset of limit set of the
2957 controlled process.
2958 .sp
2959 Any of the uids of the target process are 0 or an attempt was made to change
2960 any of the uids to 0 using PCSCRED and the security policy imposed additional
2961 restrictions. See \fBprivileges\fR(5).
2962 .RE
2963
2964 .SH NOTES
2965 .LP
2966 Descriptions of structures in this document include only interesting structure
2967 elements, not filler and padding fields, and may show elements out of order for
2968 descriptive clarity. The actual structure definitions are contained in
2969 \fB<procfs.h>\fR\&.
2970 .SH BUGS
2971 .LP
2972 Because the old \fBioctl\fR(2)-based version of \fB/proc\fR is currently
2973 supported for binary compatibility with old applications, the top-level
2974 directory for a process, \fB/proc/\fR\fIpid\fR, is not world-readable, but it
2975 is world-searchable. Thus, anyone can open \fB/proc/\fR\fIpid\fR\fB/psinfo\fR
2976 even though \fBls\fR(1) applied to \fB/proc/\fR\fIpid\fR will fail for anyone
2977 but the owner or an appropriately privileged process. Support for the old
2978 \fBioctl\fR(2)-based version of \fB/proc\fR will be dropped in a future
2979 release, at which time the top-level directory for a process will be made
2980 world-readable.
2981 .sp
2982 .LP
2983 On SPARC based machines, the types \fBgregset_t\fR and \fBfpregset_t\fR defined
2984 in <\fBsys/regset.h\fR> are similar to but not the same as the types
2985 \fBprgregset_t\fR and \fBprfpregset_t\fR defined in <\fBprocfs.h\fR>.