Lesson 17 of 20

6 mins read

Defensive Error Handling, errno & Assertions

In Plain English

When standard library or OS system calls fail, they populate the global errno integer variable. Inspect human-readable descriptions via strerror(errno) or perror(). Use <assert.h> to enforce invariant preconditions during development.

The Mental Model

"errno is the error diagnostic readout on a car dashboard: a code like 2 means "No such file or directory" (fuel cap loose)."

Deep Dive: How It Works

errno: Thread-local integer updated by failed POSIX system calls.

strerror() & perror(): Translate integer error numbers into human-readable strings.

assert(): Enforces preconditions; compiled out in release builds when -DNDEBUG is set.

Syntax Blueprint

#include <errno.h>
#include <string.h>

printf("Error: %s\n", strerror(errno));

Include errno.h and format human-readable error strings with strerror.

Core Rules to Remember

Zero Overhead in Production: Assertions can be disabled in production releases using -DNDEBUG.

Explicit Return Codes: C functions typically return 0 or non-negative on success, and -1 or NULL on failure.

Thread Safety: In modern C, errno is thread-safe and isolated per thread.

Common Beginner Traps & How to Fix Them

Mistake:Checking errno without first checking if the function call actually returned a failure indicator.

Why it happens: errno is not reset to 0 by successful calls; reading it without a preceding failure gives stale errors.

How to fix: Only inspect errno if the function returned NULL or -1.

Pro Tip: Use assertions generously to validate that incoming pointer arguments are non-NULL before proceeding.

Live Interactive Example

Hit Run Code to see it live

Translate System Error Codes

C11 / GCC 9.2

Output Console

Click "Run Code" to view the rendered output.

How it works: strerror(2) translates standard POSIX ENOENT error code into human text.

Your Turn: Micro Challenge

No pressure! Edit the starter code below and test your solution with instant feedback.

Micro Exercise

Confirm Error Verification

Print "Error Checked: TRUE\n" after strerror output.

Sandbox Output

Click "Run & Check" to test your solution.

Finished reading and practicing?

Mark this lesson as completed to update your course progress.