| 0 | Success |
| 1 | Error |
| No further detail, but typically happens with invalid/inconsistent parameters passed into Nuke. |
| -11 | Meaning not available |
| 100 | Licence error |
| 125 | Meaning not available |
| 127 | ‘nuke.pc’ not found in the pkg-config |
| This error could occur because the directory containing ‘nuke.pc’ was not found in the pkg-config search path. |
| 132 | Illegal instruction |
| 134 | Aborted |
| May include Backtrace and Memory map in logs. |
| 135 | Bus error |
| Also known as SIGBUS and is usually signal 10, occur when a process is trying to access memory that the CPU cannot physically address. In other words, the memory tried to access by the program is not a valid memory address. It’s caused due to alignment issues with the CPU (eg. trying to read a long from an address that isn’t a multiple of 4). SIGBUS is the abbreviation for ‘Bus Error’. |
| Source - https://www.geeksforgeeks.org/segmentation-fault-sigsegv-vs-bus-error-sigbus/ |
| 137 | Killed |
| 139 | Segmentation fault |
| Also known as SIGSEGV and is usually signal 11, occur when the program tries to write/read outside the memory allocated for it or when writing memory that can only be read. In other words when the program tries to access the memory to which it doesn’t have access. SIGSEGV is the abbreviation for ‘Segmentation Violation’. |
| Source - https://www.geeksforgeeks.org/segmentation-fault-sigsegv-vs-bus-error-sigbus/ |
| 256 | Permission denied |