Difference between revisions of "Process exited with code 4"
From BOINC Wiki
(Saving FAQ 283) |
(adding table) |
||
| Line 8: | Line 8: | ||
Always report this error on the project's forums. The developers will want to know about it and fix it. | Always report this error on the project's forums. The developers will want to know about it and fix it. | ||
| + | |||
| + | |||
| + | {| class="wikitable" style="text-align: center;" | ||
| + | ! Original writer | ||
| + | ! Original FAQ | ||
| + | ! Date | ||
| + | |- | ||
| Jorden | | Jorden | ||
| − | | | + | | [http://boincfaq.mundayweb.com/index.php?language=1&view=283 283] |
| − | + | | 02-10-2007 | |
| − | + | |- | |
| − | + | |} | |
| − | |||
| − | |||
| − | |||
| − | | | ||
| − | | | ||
| − | | | ||
Latest revision as of 22:18, 29 August 2016
With thanks to Bernd Machenschalk of Einstein for this explanation.
In general there are two reasons for an exit code 4:
- a signal 4 (illegal instruction) happens when the application tries to execute commands the CPU isn't capable of (e.g. AltiVec code running on a G3 Mac)
- an error in the command-line that is passed from the Client to the application. Typically something went wrong in the communication of the Core Client, talking to either the server, the application or the file-system of the host.
Always report this error on the project's forums. The developers will want to know about it and fix it.
| Original writer | Original FAQ | Date |
|---|---|---|
| Jorden | 283 | 02-10-2007 |
