is a header file in the standard library of the C programming language. It defines macros for reporting and retrieving error conditions using the symbol <code>errno</code> (short form for "error number").
<code>errno</code> acts like an integer variable. A value (the error number) is stored in <code>errno</code> by certain library functions when they detect errors. At program startup, the value stored is zero. Library functions store only values greater than zero. Any library function can alter the value stored before return, whether or not they detect errors. Most functions indicate that they detected an error by returning a special value, typically for functions that return pointers, and for functions that return integers. A few functions require the caller to preset <code>errno</code> to zero and test it afterwards to see if an error was detected.
The <code>errno</code> macro expands to an lvalue with type <code>int</code>, sometimes with the <code>extern</code> and/or <code>volatile</code> type specifiers depending upon the platform. Originally this was a static memory location, but macros are almost always used today to allow for multi-threading, so that each thread will see its own thread-local error number.
The header file also defines macros that expand to integer constants that represent the error codes. The C standard library only requires three to be defined:
POSIX compliant operating systems like AIX, Linux or Solaris include many other error values, many of which are used much more often than the above ones, such as for when a file cannot be opened for reading. C++11 additionally defines many of the same values found within the POSIX specification.
Traditionally, the first page of Unix system manuals, named intro(2), lists all errno.h macros, but this is not the case with Linux, where these macros are instead listed in the errno(3).
An can be translated to a descriptive string using (defined in ) or a BSD extension called . The translation can be printed directly to the standard error stream using (defined in ). As in many Unix-like systems is not thread-safe, a thread-safe version is used, but conflicting definitions from POSIX and GNU makes it even less portable than the table.
The GNU C library (GLIBC) provides the additional POSIX error values macros in the header file . These are the descriptions of the macros provided by .
The macro names and meanings for error codes are defined in the POSIX Standards definition however the numeric values are NOT, though by convention the values appear to be the same across different versions of Unix. Programs should not rely on specific numeric values and should test code using the macro names specified in the ERRORS section of the man page of the associated function. For source code readability and portability the use of the standard macro names in code is highly recommended.