libexplain  1.4.D001
Functions
libexplain/munmap.h File Reference

explain munmap(2) errors More...

#include <libexplain/gcc_attributes.h>
#include <libexplain/large_file_support.h>
#include <sys/mman.h>

Go to the source code of this file.

Functions

void explain_munmap_or_die (void *data, size_t data_size)
int explain_munmap_on_error (void *data, size_t data_size)
const char * explain_munmap (void *data, size_t data_size) LIBEXPLAIN_WARN_UNUSED_RESULT
const char * explain_errno_munmap (int errnum, void *data, size_t data_size) LIBEXPLAIN_WARN_UNUSED_RESULT
void explain_message_munmap (char *message, int message_size, void *data, size_t data_size)
void explain_message_errno_munmap (char *message, int message_size, int errnum, void *data, size_t data_size)

Detailed Description

explain munmap(2) errors

These functions may be used to obtain explanations for errors returned by the munmap(2) system call.

Definition in file munmap.h.


Function Documentation

const char* explain_errno_munmap ( int  errnum,
void *  data,
size_t  data_size 
)

The explain_errno_munmap function is used to obtain an explanation of an error returned by the munmap(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.

Parameters:
errnumThe error value to be decoded, usually obtained from the errno global variable just before this function is called. This is necessary if you need to call any code between the system call to be explained and this function, because many libc functions will alter the value of errno.
dataThe original data, exactly as passed to the munmap(2) system call.
data_sizeThe original data_size, exactly as passed to the munmap(2) system call.
Returns:
The message explaining the error. This message buffer is shared by all libexplain functions which do not supply a buffer in their argument list. This will be overwritten by the next call to any libexplain function which shares this buffer, including other threads.
Note:
This function is not thread safe, because it shares a return buffer across all threads, and many other functions in this library.
Example:
This function is intended to be used in a fashion similar to the following example:
 if (munmap(data, data_size) < 0)
 {
     int err = errno;
     fprintf(stderr, "%s\n", explain_errno_munmap(err, data, data_size));
     exit(EXIT_FAILURE);
 }
The above code example is available pre-packaged as the explain_munmap_or_die function.
void explain_message_errno_munmap ( char *  message,
int  message_size,
int  errnum,
void *  data,
size_t  data_size 
)

The explain_message_errno_munmap function is used to obtain an explanation of an error returned by the munmap(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.

Parameters:
messageThe location in which to store the returned message. If a suitable message return buffer is supplied, this function is thread safe.
message_sizeThe size in bytes of the location in which to store the returned message.
errnumThe error value to be decoded, usually obtained from the errno global variable just before this function is called. This is necessary if you need to call any code between the system call to be explained and this function, because many libc functions will alter the value of errno.
dataThe original data, exactly as passed to the munmap(2) system call.
data_sizeThe original data_size, exactly as passed to the munmap(2) system call.
Example:
This function is intended to be used in a fashion similar to the following example:
 if (munmap(data, data_size) < 0)
 {
     int err = errno;
     char message[3000];
     explain_message_errno_munmap(message, sizeof(message), err, data,
         data_size);
     fprintf(stderr, "%s\n", message);
     exit(EXIT_FAILURE);
 }
The above code example is available pre-packaged as the explain_munmap_or_die function.
void explain_message_munmap ( char *  message,
int  message_size,
void *  data,
size_t  data_size 
)

The explain_message_munmap function is used to obtain an explanation of an error returned by the munmap(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.

The errno global variable will be used to obtain the error value to be decoded.

Parameters:
messageThe location in which to store the returned message. If a suitable message return buffer is supplied, this function is thread safe.
message_sizeThe size in bytes of the location in which to store the returned message.
dataThe original data, exactly as passed to the munmap(2) system call.
data_sizeThe original data_size, exactly as passed to the munmap(2) system call.
Example:
This function is intended to be used in a fashion similar to the following example:
 if (munmap(data, data_size) < 0)
 {
     char message[3000];
     explain_message_munmap(message, sizeof(message), data, data_size);
     fprintf(stderr, "%s\n", message);
     exit(EXIT_FAILURE);
 }
The above code example is available pre-packaged as the explain_munmap_or_die function.
const char* explain_munmap ( void *  data,
size_t  data_size 
)

The explain_munmap function is used to obtain an explanation of an error returned by the munmap(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.

Parameters:
dataThe original data, exactly as passed to the munmap(2) system call.
data_sizeThe original data_size, exactly as passed to the munmap(2) system call.
Returns:
The message explaining the error. This message buffer is shared by all libexplain functions which do not supply a buffer in their argument list. This will be overwritten by the next call to any libexplain function which shares this buffer, including other threads.
Note:
This function is not thread safe, because it shares a return buffer across all threads, and many other functions in this library.
Example:
This function is intended to be used in a fashion similar to the following example:
 if (munmap(data, data_size) < 0)
 {
     fprintf(stderr, "%s\n", explain_munmap(data, data_size));
     exit(EXIT_FAILURE);
 }
The above code example is available pre-packaged as the explain_munmap_or_die function.
int explain_munmap_on_error ( void *  data,
size_t  data_size 
)

The explain_munmap_on_error function is used to call the munmap(2) system call. On failure an explanation will be printed to stderr, obtained from the explain_munmap(3) function.

Parameters:
dataThe data, exactly as to be passed to the munmap(2) system call.
data_sizeThe data_size, exactly as to be passed to the munmap(2) system call.
Returns:
The value returned by the wrapped munmap(2) system call.
Example:
This function is intended to be used in a fashion similar to the following example:
 if (explain_munmap_on_error(data, data_size) < 0)
 {
     ...cope with error
     ...no need to print error message
 }
void explain_munmap_or_die ( void *  data,
size_t  data_size 
)

The explain_munmap_or_die function is used to call the munmap(2) system call. On failure an explanation will be printed to stderr, obtained from the explain_munmap(3) function, and then the process terminates by calling exit(EXIT_FAILURE).

Parameters:
dataThe data, exactly as to be passed to the munmap(2) system call.
data_sizeThe data_size, exactly as to be passed to the munmap(2) system call.
Returns:
This function only returns on success, see munmap(2) for more information. On failure, prints an explanation and exits, it does not return.
Example:
This function is intended to be used in a fashion similar to the following example:
 explain_munmap_or_die(data, data_size);