Exit Codes in C and C++ Programs

When a C or C++ application finishes running, it sends back a numeric value to the operating system. This value is called an exit code. Exit codes tell us whether the program ran without problems or hit some kind of error along the way.

How the exit() Function Works in C and C++

The exit() function stops a program right where it is. It accepts a single integer argument, which becomes the program’s return value.

void exit(int return_code)

A return value of 0 (or EXIT_SUCCESS) means the program completed as expected. Any non-zero return value (or EXIT_FAILURE) signals that something went wrong. Among all possible exit codes, values 1, 2, 126 through 165, and 255 carry predefined meanings. Avoid picking these numbers for your own custom codes.

Common Exit Codes in C/C++ and Their Meanings

The table below lists widely recognized exit codes and what each one signals.

These exit codes make troubleshooting much easier. If your program returns 139, for instance, you know it attempted to reach a memory address it had no permission to touch. Start fixing pointer-related bugs from there.

Practical Scenarios That Produce Specific Exit Codes

Accessing an Array Beyond Its Bounds (Exit Code 139)

Declaring an array with 100 slots but trying to read position 100001 triggers a segmentation fault. The operating system halts the program because it tried to reach restricted memory space.

int arr[100] = {0};
cout << arr[100001];  // causes segmentation fault

Dividing an Integer by Zero (Exit Code 136)

Attempting to compute a / b when b holds the value zero raises a floating-point signal. The system terminates the process and returns exit code 136.

int a = 1, b = 0;
cout << a / b;  // triggers SIGFPE

Endless Loop Consuming All Resources (Exit Code 137)

An infinite loop that keeps allocating local arrays on every iteration exhausts available memory fast. The system kills the process once resource limits are breached.

for (;;) {
    int arr[10000];
}

Why Exit Codes in C and C++ Matter for Debugging

Exit codes give programmers a quick way to identify the category of failure without reading through log files. When an application crashes during automated testing or production deployment, the returned exit code often points straight to the root cause.

A code of 139 means pointer misuse. A code of 136 means arithmetic gone wrong. A code of 137 means your program ate more memory than allowed.

Getting familiar with standard exit codes saves real debugging time, especially when working on large codebases or multi-process systems where one crashed component can affect everything else.