Manual Pages  — ASSERT

#include <assert.h>

The assert() macro tests the given expression and if it is false, the calling process is terminated. A diagnostic message is written to stderr and the function abort(3) is called, effectively terminating the program.

If expression is true, the assert() macro does nothing.

The assert() macro may be removed at compile time by defining NDEBUG as a macro (e.g., by using the cc(1) option -D NDEBUG). Unlike most other include files, <assert.h> may be included multiple times. Each time whether or not NDEBUG is defined determines the behavior of assert from that point forward until the end of the unit or another include of <assert.h>.

The assert() macro should only be used for ensuring the developer's expectations hold true. It is not appropriate for regular run-time error detection.

The static_assert() macro expands to _Static_assert(), and, contrarily to assert(), makes assertions at compile-time. Once the constraint is violated, the compiler produces a diagnostic message including the string literal message, if provided. The initial form of the _Static_assert() containing a string literal message was introduced in C11 standard, and the other form with no string literal is to be implemented by C2x and some compilers may lack its adoption at present.

abort2(2), abort(3)