assert(3)

assert3

Abort the program if assertion is false

Usage

#include <assert.h>

void assert(bool expression);

Library

Standard C library (libc, -lc)

Overview

This macro can help programmers find bugs in their programs, or handle exceptional cases via a crash that will produce limited debugging output.

If expression is false (i.e., compares equal to zero), assert() prints an error message to standard error and terminates the program by calling abort(3). The error message includes the name of the file and function containing the assert() call, the source code line number of the call, and the text of the argument; something like:

prog: some_file.c:16: some_func: Assertion `val == 0' failed.

If the macro NDEBUG is defined at the moment <assert.h> was last included, the macro assert() generates no code, and hence does nothing at all. It is not recommended to define NDEBUG if using assert() to detect error conditions since the software may behave non-deterministically.

Return value

No value is returned.

Attributes

For an explanation of the terms used in this section, see attributes(7).

InterfaceAttributeValue
assert()Thread safetyMT-Safe

Releases

19 releases since Debian 1.1 (Buzz); the text changed 14 times.

  1. 1.1–1.2
  2. 1.3–2.2
  3. 3.0
  4. 3.1
  5. 4.0
  6. 5.0
  7. 6.0
  8. 7
  9. 8
  10. 9
  11. 10
  12. 11
  13. 12
  14. 13
  15. Arch

Standards

C11, POSIX.1-2008.

History

C89, C99, POSIX.1-2001.

In C89, expression is required to be of type int and undefined behavior results if it is not, but in C99 it may have any scalar type.

Bugs

assert() is implemented as a macro; if the expression tested has side-effects, program behavior will be different depending on whether NDEBUG is defined. This may create Heisenbugs which go away when debugging is turned on.

From man-pages 6.19-1 in Arch Linux 2026-11-01. Parsed by carta from the page's man source.