Exit 135 SIGBUS (128 + 7)
Killed by SIGBUS: a bad memory access that is not a plain segfault.
- Value
- 135
- Convention
- Killed by a signal (128 + N)
- Signal
- SIGBUS (Linux 7, FreeBSD 10)
Typical causes: touching a mmap()ed file page after the file was truncated, unaligned access on strict architectures, or a failed read-in from a file or network-backed mapping. Note the number: SIGBUS is 7 on Linux x86 (exit 135) but 10 on FreeBSD (exit 138).
What to check
dmesg | tail; ls -l the-mapped-fileSources
Exit codes are conventions, not guarantees: a program can return any value from 0 to 255. Spot one that's wrong? Tell Rod.