01
Identify the namespace
Choose Bash status, signal, errno or syscall before searching. A decimal query matches exactly in that category; typing 2 will not silently become four unrelated answers.
Developer reference
Linux exit codeswith signals and system constants
Choose the kind of number first, then search a name or decimal value in a source-checked, curated table.
Linux exit codes
Matching entries
137
Number: 137
Meaning: Could indicate Bash's 128+9 convention for SIGKILL; it does not by itself prove OOM.
Bash may use 128 plus a signal number after fatal termination. A program can also return the same number itself; 137 alone does not prove OOM.
Check on your machine
kill -l 137Queries use the built-in table in this browser; external sources open only when you choose a link.
Reference options
Number type
System: Linux. The selected kernel tag affects system-call availability; this page does not inspect your device.
Showing 1 matches from 9 curated entries
Source values checked 23 Sep 2026
A failed deployment may show 137, an errno name or a raw syscall number. Linux exit codes are useful clues, but these are three different namespaces. Select the one your log actually reports before interpreting a number.
This reference brings Linux signals, errno numbers and syscall numbers beside Bash exit status. It labels the architecture and fixed kernel snapshot so a convenient lookup does not become a claim about your running machine.
Why use this Linux exit codes reference
The same number can answer different questions depending on its namespace and machine.
Give a number its context
The number 2 can mean SIGINT, ENOENT, an x86-64 open syscall, or a program's own exit status. This Linux exit codes reference keeps the four domains separate instead of guessing from a bare integer.
See architecture and release boundaries
The read syscall is 0 on x86-64 and 63 on arm64. A kernel tag also changes which calls appear. The selected source snapshot remains visible so you can verify a number against the target system.
Three checks before trusting a number
02
Match the target ABI
Pick x86-64 or arm64 and a pinned kernel tag. System-call entries can change or disappear across snapshots; Bash status rules do not change with this selector.
03
Verify on the real machine
Use the displayed read-only check command or source link. For 137, inspect process or kernel logs before calling it an OOM event; this table cannot observe how that process ended.
Four useful namespaces in one lookup
Bash status clues
Linux exit codes 126 and 127 have Bash-specific meanings. Values above 128 may correspond to signals, but an application can deliberately return the same value.
Signals and error names
The curated Linux signals show their default action; errno entries pair names and numbers, including the EAGAIN and EWOULDBLOCK alias.
Source-pinned system calls
Compare syscall numbers across x86-64 and arm64 in Linux v6.6 or v6.16 source tables, including a newer call that is absent from the older snapshot.
What a static table cannot infer
- No universal meaning for 137
- Linux exit codes show what a shell or program reported. A 137 value fits Bash's 128+SIGKILL convention, but can also be returned intentionally; OOM needs independent log evidence.
- Curated snapshots, not live detection
- Only selected x86-64 and arm64 values are included. A missing symbol is not proof it does not exist on another kernel, architecture or libc; follow the original source.
- No errno-to-HTTP conversion
- An errno such as ENOENT is a local call error, not a standard HTTP 404. Each application decides how, or whether, to translate it into an HTTP response.
- No commands executed
- The page does not send signals, make system calls, read your running kernel or upload logs. It only shows and copies inspection commands for you to run deliberately.
Linux exit codes questions
What does exit code 137 mean in Linux?
Bash uses 128 plus the fatal signal number, so 137 can point to SIGKILL (9). A program may also exit with 137 by choice. Inspect wait status and kernel or container logs before concluding that OOM caused it.
Why does a command return exit code 127?
Bash returns 127 when it cannot find the command. Check the name and PATH. Code 126 instead means the command was found but could not be executed.
How do I look up a Linux errno number?
Choose errno, enter the decimal value or symbolic name, and check the architecture. On a Linux machine with moreutils installed, errno 2 or errno ENOENT gives the local mapping.
Are Linux signal numbers the same on every architecture?
No. Several signal numbers differ on architectures outside this page's x86-64 and arm64 scope. Prefer symbolic names in scripts and inspect signal(7) or kill -l on the target machine.
Where can I find a Linux syscall number?
Choose System call and the architecture and kernel snapshot, then open the linked kernel table. The same call can have different numbers; read is 0 on x86-64 and 63 on arm64 here.
Found a missing or incorrect entry?
Check Linux exit codes with context
Search a curated entry, compare its source and use the local check command when your actual machine matters.
Static reference data is searched in your browser.