Difference between revisions of "Application exit codes"
(removing broken link to original faq)
|Line 47:||Line 47:|
Latest revision as of 21:32, 16 August 2017
- 0. SUCCESS
Not an error message. It's a success message. Rejoice!
- -1. CANT_CREATE_FILE
Cannot make a file, due to problems with the write directory. Directory may be hidden, or its contents set to read-only. Or permission is just not allowed.
- -2. READ_FAILED
Cannot read file. Is the file even there? Is the file corrupt?
- -3. WRITE_FAILED
Cannot write the file. Is there enough drive space to write the file into? Do you have permission to write to the directory? Are the contents of the directory set to read-only?
- -4. MALLOC_FAILED
Memory allocation failed. Do you have enough memory? Is the application appointing a memory write point within your available memory?
- -5. FOPEN_FAILED
File Open has failed. Make sure you have read/write rights to the whole BOINC directory and sub directories, that all files are not read-only.
On BOINC 5 versions, make sure the BOINC directory isn't hidden.
- -6. BAD_HEADER
This is a network connection error and can happen when you try to use TLS/SSL authentication while the server is not set up for TLS/SSL, or vice versa.
- -7. BAD_DECODE
Application ran out of memory during the decode, file ended too soon, too many bad lines - rejecting file, encoded line has bad length.
- -8. BAD_BIN_READ
Bad binary task.
- -9. RESULT_OVERFLOW
In the Seti project this is a benign error. It means that there were more radio signals found than there is space in the output file to store them in. This is most usually caused by extra terrestrial Radio Frequency Interference (RFI) signals. Not aliens.
- -10. UNHANDLED_SIGNAL
- -11. FP_ERROR
Floating Point error.
- -12. ATEXIT_FAILURE
Task failed at exit.
|Original writer||Original FAQ||Date|