PERROR_PRINTF(3PROC) Process Control Library Functions PERROR_PRINTF(3PROC)
Perror_printf - interposable function for additional diagnostics
Process Control Library (libproc, -lproc)
#include <libproc.h>
void
Perror_printf(struct ps_prochandle *P, const char *format, ...);
The Perror_printf() function allows for consumers of the libproc
library to obtain additional diagnostic information during various
operations. Consumers must explicitly interpose on this symbol and
provide their own definition, if desired. There is no requirement for
such an interposition to be done. When called, P will be the process
handle that the additional diagnostics are being generated for and the
diagnostics will be provided in a printf(3C) style.
Uncommitted
While the interposing interface is uncommitted, the provided
diagnostics are Not-an-Interface and may change at any time.
Callers should presume that this function may be called from multiple
threads and always in a context in which taking locks is fine. Callers
should not expect to be called from a signal handler.
libproc(3LIB)
illumos November 27, 2023 illumos
NAME
Perror_printf - interposable function for additional diagnostics
LIBRARY
Process Control Library (libproc, -lproc)
SYNOPSIS
#include <libproc.h>
void
Perror_printf(struct ps_prochandle *P, const char *format, ...);
DESCRIPTION
The Perror_printf() function allows for consumers of the libproc
library to obtain additional diagnostic information during various
operations. Consumers must explicitly interpose on this symbol and
provide their own definition, if desired. There is no requirement for
such an interposition to be done. When called, P will be the process
handle that the additional diagnostics are being generated for and the
diagnostics will be provided in a printf(3C) style.
INTERFACE STABILITY
Uncommitted
While the interposing interface is uncommitted, the provided
diagnostics are Not-an-Interface and may change at any time.
LOCKING
Callers should presume that this function may be called from multiple
threads and always in a context in which taking locks is fine. Callers
should not expect to be called from a signal handler.
SEE ALSO
libproc(3LIB)
illumos November 27, 2023 illumos