Gnu Error Codes
Contents |
integer values. Error codes above 1024 are reserved for linux kernel error codes applications, and are not used by the library. Many
C Programming Error Codes
of the error codes use the same base name as the corresponding error code eintr errno in the C library. Here are some of the most common error codes, Macro: int GSL_EDOM Domain error; used by mathematical functions when an enosys error argument value does not fall into the domain over which the function is defined (like EDOM in the C library) Macro: int GSL_ERANGE Range error; used by mathematical functions when the result value is not representable because of overflow or underflow (like ERANGE in the C library)
Eintr Signal
Macro: int GSL_ENOMEM No memory available. The system cannot allocate more virtual memory because its capacity is full (like ENOMEM in the C library). This error is reported when a GSL routine encounters problems when trying to allocate memory with malloc. Macro: int GSL_EINVAL Invalid argument. This is used to indicate various kinds of problems with passing the wrong argument to a library function (like EINVAL in the C library). The error codes can be converted into an error message using the function gsl_strerror. Function: const char * gsl_strerror (const int gsl_errno) This function returns a pointer to a string describing the error code gsl_errno. For example, printf ("error: %s\n", gsl_strerror (status)); would print an error message like error: output range error for a status value of GSL_ERANGE. Next: Error Handlers, Previous: Error Reporting, Up: Error Handling [Index]
of a library call. The functions strerror and perror give you the standard error message for a given error code; the variable program_invocation_short_name gives you convenient c error function access to the name of the program that encountered the error. Function: eio error in c char * strerror (int errnum) Preliminary: | MT-Unsafe race:strerror | AS-Unsafe heap i18n | AC-Unsafe mem | See POSIX
Posix Error Codes
Safety Concepts. The strerror function maps the error code (see Checking for Errors) specified by the errnum argument to a descriptive error message string. The return value is a pointer to https://www.gnu.org/s/gsl/manual/html_node/Error-Codes.html this string. The value errnum normally comes from the variable errno. You should not modify the string returned by strerror. Also, if you make subsequent calls to strerror, the string might be overwritten. (But it’s guaranteed that no library function ever calls strerror behind your back.) The function strerror is declared in string.h. Function: char * strerror_r (int errnum, char *buf, size_t n) http://www.gnu.org/s/libc/manual/html_node/Error-Messages.html Preliminary: | MT-Safe | AS-Unsafe i18n | AC-Unsafe | See POSIX Safety Concepts. The strerror_r function works like strerror but instead of returning the error message in a statically allocated buffer shared by all threads in the process, it returns a private copy for the thread. This might be either some permanent global data or a message string in the user supplied buffer starting at buf with the length of n bytes. At most n characters are written (including the NUL byte) so it is up to the user to select a buffer large enough. This function should always be used in multi-threaded programs since there is no way to guarantee the string returned by strerror really belongs to the last call of the current thread. The function strerror_r is a GNU extension and it is declared in string.h. Function: void perror (const char *message) Preliminary: | MT-Safe race:stderr | AS-Unsafe corrupt i18n heap lock | AC-Unsafe corrupt lock mem fd | See POSIX Safety Concepts. This function prints an error message to the stream stderr; see Standard Streams. The orientation of stderr is not
indicates the end of a list, buffer or file. GPG_ERR_NO_ERROR This value indicates success. The value of this error code is 0. Also, it is guaranteed that an error https://gnupg.org/documentation/manuals/gcrypt/Error-Codes.html value made from the error code 0 will be 0 itself (as http://unix.stackexchange.com/questions/18807/where-can-i-find-a-list-of-make-error-codes a whole). This means that the error source information is lost for this error code, however, as this error code indicates that no error occurred, this is generally not a problem. GPG_ERR_GENERAL This value means that something went wrong, but either there is not enough information about the error codes problem to return a more useful error value, or there is no separate error value for this type of problem. GPG_ERR_ENOMEM This value means that an out-of-memory condition occurred. GPG_ERR_E... System errors are mapped to GPG_ERR_EFOO where FOO is the symbol for the system error. GPG_ERR_INV_VALUE This value means that some user provided data was out of range. GPG_ERR_UNUSABLE_PUBKEY This value gnu error codes means that some recipients for a message were invalid. GPG_ERR_UNUSABLE_SECKEY This value means that some signers were invalid. GPG_ERR_NO_DATA This value means that data was expected where no data was found. GPG_ERR_CONFLICT This value means that a conflict of some sort occurred. GPG_ERR_NOT_IMPLEMENTED This value indicates that the specific function (or operation) is not implemented. This error should never happen. It can only occur if you use certain values or configuration options which do not work, but for which we think that they should work at some later time. GPG_ERR_DECRYPT_FAILED This value indicates that a decryption operation was unsuccessful. GPG_ERR_WRONG_KEY_USAGE This value indicates that a key is not used appropriately. GPG_ERR_NO_SECKEY This value indicates that no secret key for the user ID is available. GPG_ERR_UNSUPPORTED_ALGORITHM This value means a verification failed because the cryptographic algorithm is not supported by the crypto backend. GPG_ERR_BAD_SIGNATURE This value means a verification failed because the signature is bad. GPG_ERR_NO_PUBKEY This value means a verification failed because the public key is not available. GPG_ERR_NOT_OPERATIONAL This value means that the library is not yet in state which
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Unix & Linux Questions Tags Users Badges Unanswered Ask Question _ Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Where can I find a list of 'make' error codes? up vote 14 down vote favorite 5 I am trying to compile a program written in Fortran using make (I have a Makefile and, while in the directory containing the Makefile, I type the command $ make target, where "target" is a system-specific target specification is present in my Makefile. As I experiment with various revisions of my target specification, I often get a variety of error messages when attempting to call make. To give a few examples: make[1]: Entering directory /bin/sh: line 0: test: too many arguments ./dpp angfrc.f > angfrc.tmp.f /bin/sh: ./dpp: Permission denied make[1]: *** [angfrc.o] Error 126 make[1]: Leaving directory make: *** [cmu60] Error 2 and make[1]: Entering directory /bin/sh: line 0: test: too many arguments ./dpp -DSTRESS -DMPI -P -D'pointer=integer'-I/opt/mpich_intel/include angfrc.f > angfrc.tmp.f /bin/sh: ./dpp: Permission denied make[1]: *** [angfrc.o] Error 126 make[1]: Leaving directory make: *** [mpich-c2] Error 2 and make[1]: Entering directory /bin/sh: line 0: test: too many arguments ./dpp -DSTRESS -DMPI -P -D'pointer=integer' -I/opt/mpich_intel/include angfrc.f > angfrc.tmp.f /bin/sh: ./dpp: Permission denied make[1]: *** [angfrc.o] Error 126 make[1]: Leaving directory make: *** [mpi-intel] Error 2 Do you know how I can find a list of what the error codes, such as "Error 126" and "Error 2," mean? I found this thread on another website, but I am not sure what the reply means. Does it mean that there is no system-independent meaning of the make error codes? Can you please help me? Thank you. make error-handling gnu-make share|improve this question edited Aug 15 '11 at 22:04 Gilles 372k696751126 asked Aug 15 '11 at 21:46 Andrew 2,400224467 opussoftware.com/manual/appendices/B1.htm has a list... –Wilf Jul 30 '15 at 2:08 add a comment| 2 Answers 2 active oldest votes up vote 18 down vote accepted The error codes aren't from make: make is reporting the return status of the command that failed. You need