SIGABRT (Signal 6): Meaning, Exit Code 134 & Fix
SIGABRT is Unix signal 6. A process terminated by it reports exit code 134 (128 + 6).
SIGABRT is raised by abort(), typically from a failed assertion or a fatal runtime error. When it kills a process, the shell reports exit code 134 - the 128 + signal-number convention.
What it means
A C/C++ assertion, glibc heap-corruption detection, C++ std::terminate, or a runtime panic configured to abort.
When it happens in CI
- glibc detected heap corruption ("free(): invalid pointer").
- A failed
assert(). - An unhandled C++ exception → std::terminate.
How to handle it
Read stderr above the abort for the specific message; this is a real bug, not a transient failure. Reproduce with debug symbols.
Related guides
Docker Build Exit Code 137 (OOM Killed) - Fix Out-of-Memory BuildsDocker build or container exiting with code 137 means the process was OOM-killed. Learn why it happens in CI…
SIGFPE (Signal 8): Meaning, Exit Code 136 & FixWhat SIGFPE (signal 8) means in CI: an arithmetic exception, usually integer divide-by-zero. A process killed…
SIGTERM (Signal 15): Meaning, Exit Code 143 & FixWhat SIGTERM (signal 15) means in CI: a graceful termination request. A process killed by it exits with code…