Defined in header <string.h> | ||
---|---|---|
char* strerror( int errnum ); | (1) | |
errno_t strerror_s( char *buf, rsize_t bufsz, errno_t errnum ); | (2) | (since C11) |
size_t strerrorlen_s( errno_t errnum ); | (3) | (since C11) |
errnum
, identical to the description that would be printed by perror()
.errnum
is usually acquired from the errno
variable, however the function accepts any value of type int
. The contents of the string are locale-specific.strerror
function. strerror
is not required to be thread-safe. Implementations may be returning different pointers to static read-only string literals or may be returning the same pointer over and over, pointing at a static buffer in which strerror places the string.buf
. No more than bufsz-1
bytes are written, the buffer is always null-terminated. If the message had to be truncated to fit the buffer and bufsz
is greater than 3, then only bufsz-4
bytes are written, and the characters "..."
are appended before the null terminator. In addition, the following errors are detected at runtime and call the currently installed constraint handler function: buf
is a null pointer bufsz
is zero or greater than RSIZE_MAX
buf
occurs past the end of the array, which can happen when the size of the buffer pointed to by buf
is less than the number of characters in the error message which in turn is less than bufsz
.strerror_s
would write if it were called with errnum
. The length does not include the null terminator. As with all bounds-checked functions, strerror_s
and strerrorlen_s
are only guaranteed to be available if __STDC_LIB_EXT1__
is defined by the implementation and if the user defines __STDC_WANT_LIB_EXT1__
to the integer constant 1 before including string.h
.errnum | - | integral value referring to an error code |
buf | - | pointer to a user-provided buffer |
bufsz | - | size of the user-provided buffer |
buf
, non-zero otherwise.strerror_s
would returnPOSIX allows subsequent calls to strerror
to invalidate the pointer value returned by an earlier call. It also specifies that it is the LC_MESSAGES
locale facet that controls the contents of these messages.
strerror_s
is the only bounds-checked function that allows truncation, because providing as much information as possible about a failure was deemed to be more desirable. POSIX also defines strerror_r for similar purposes.
#define __STDC_WANT_LIB_EXT1__ 1 #include <stdio.h> #include <errno.h> #include <string.h> #include <locale.h> int main(void) { FILE *fp = fopen(tmpnam((char[L_tmpnam]){0}), "r"); if(fp==NULL) { printf("File opening error: %s\n", strerror(errno)); setlocale(LC_MESSAGES, "de_DE.utf8"); printf("Now in German: %s\n", strerror(errno)); #ifdef __STDC_LIB_EXT1__ setlocale(LC_ALL, "ja_JP.utf8"); // printf needs CTYPE for multibyte output size_t errmsglen = strerrorlen_s(errno) + 1; char errmsg[errmsglen]; strerror_s(errmsg, errmsglen, errno); printf("Now in Japanese: %s\n", errmsg); #endif } }
Possible output:
File opening error: No such file or directory Now in German: Datei oder Verzeichnis nicht gefunden Now in Japanese: そのようなファイル、又はディレクトリはありません
displays a character string corresponding of the current error to stderr (function) |
|
macro which expands to POSIX-compatible thread-local error number variable (macro variable) |
© cppreference.com
Licensed under the Creative Commons Attribution-ShareAlike Unported License v3.0.
http://en.cppreference.com/w/c/string/byte/strerror