explain_wait4(3) | Library Functions Manual | explain_wait4(3) |
explain_wait4 - explain wait4(2) errors
#include <libexplain/wait4.h>
const char *explain_wait4(int pid, int *status, int options,
struct rusage *rusage);
const char *explain_errno_wait4(int errnum, int pid, int *status, int options,
struct rusage *rusage);
void explain_message_wait4(char *message, int message_size, int pid, int
*status, int options, struct rusage *rusage);
void explain_message_errno_wait4(char *message, int message_size, int errnum,
int pid, int *status, int options, struct rusage *rusage);
These functions may be used to obtain explanations for errors returned by the wait4(2) system call.
const char *explain_wait4(int pid, int *status, int options, struct rusage *rusage);
The explain_wait4 function is used to obtain an explanation of an error returned by the wait4(2) system call. The least the message will contain is the value of strerror(errno), but usually it will do much better, and indicate the underlying cause in more detail.
The errno global variable will be used to obtain the error value to be decoded.
This function is intended to be used in a fashion similar to the following example:
if (wait4(pid, status, options, rusage) < 0) {
fprintf(stderr, "%s\n", explain_wait4(pid, status, options, rusage));
exit(EXIT_FAILURE); }
Note: This function is not thread safe, because it shares a return buffer across all threads, and many other functions in this library.
const char *explain_errno_wait4(int errnum, int pid, int *status, int options, struct rusage *rusage);
The explain_errno_wait4 function is used to obtain an explanation of an error returned by the wait4(2) system call. The least the message will contain is the value of strerror(errnum), but usually it will do much better, and indicate the underlying cause in more detail.
This function is intended to be used in a fashion similar to the following example:
if (wait4(pid, status, options, rusage) < 0) {
int err = errno;
fprintf(stderr, "%s\n", explain_errno_wait4(err,
pid, status, options, rusage));
exit(EXIT_FAILURE); }
Note: This function is not thread safe, because it shares a return buffer across all threads, and many other functions in this library.
void explain_message_wait4(char *message, int message_size, int pid, int *status, int options, struct rusage *rusage);
The explain_message_wait4 function may be used to obtain an explanation of an error returned by the wait4(2) system call. The least the message will contain is the value of strerror(errno), but usually it will do much better, and indicate the underlying cause in more detail.
The errno global variable will be used to obtain the error value to be decoded.
This function is intended to be used in a fashion similar to the following example:
if (wait4(pid, status, options, rusage) < 0) {
char message[3000];
explain_message_wait4(message, sizeof(message),
pid, status, options, rusage);
fprintf(stderr, "%s\n", message);
exit(EXIT_FAILURE); }
void explain_message_errno_wait4(char *message, int message_size, int errnum, int pid, int *status, int options, struct rusage *rusage);
The explain_message_errno_wait4 function may be used to obtain an explanation of an error returned by the wait4(2) system call. The least the message will contain is the value of strerror(errnum), but usually it will do much better, and indicate the underlying cause in more detail.
This function is intended to be used in a fashion similar to the following example:
if (wait4(pid, status, options, rusage) < 0) {
int err = errno;
char message[3000];
explain_message_errno_wait4(message, sizeof(message), err,
pid, status, options, rusage);
fprintf(stderr, "%s\n", message);
exit(EXIT_FAILURE); }
libexplain version 1.4
Copyright (C) 2008 Peter Miller