Exit Code 133 in CI: SIGTRAP Termination Explained
Exit code 133 means SIGTRAP (128 + 5) - a trace or breakpoint trap.
A step exiting 133 hit a trap instruction. Outside a debugger this usually points at a corrupted binary or an incompatible runtime build.
What it means
133 = 128 + 5. SIGTRAP is used by debuggers and tracers at breakpoints. When no debugger is attached, a runtime hit an int3/breakpoint instruction unexpectedly.
Common causes
- A debugger or tracer was left attached in CI.
- A runtime executed a stray breakpoint instruction.
- A corrupted or tampered binary detected itself.
How to fix it
Remove debuggers/tracers from the CI path. If it persists, suspect a corrupted binary or a runtime built for a different platform; rebuild or repull the artifact.
Related guides
Exit Codes and Signals in CI/CD: A Practical GuideA practical guide to process exit codes and signals in CI/CD - what 1, 2, 124, 126, 127, 130, 137, and 143 me…
CI Exit Code Lookup: What Does This Exit Code Mean?Instant lookup for CI/CD process exit codes - enter a code (137, 127, 143…) to see what it means, whether it…