musl/src/exit/assert.c

#include <stdio.h>
#include <stdlib.h>

_Noreturn void __assert_fail(const char *expr, const char *file, int line, const char *func)
{
	fprintf(stderr, "Assertion failed: %s (%s: %s: %d)\n", expr, file, func, line);
	fflush(NULL);
	abort();
}
initial check-in, version 0.5.0 2011-02-12 00:22:29 -05:00			`#include <stdio.h>`
			`#include <stdlib.h>`

further use of _Noreturn, for non-plain-C functions note that POSIX does not specify these functions as _Noreturn, because POSIX is aligned with C99, not the new C11 standard. when POSIX is eventually updated to C11, it will almost surely give these functions the _Noreturn attribute. for now, the actual _Noreturn keyword is not used anyway when compiling with a c99 compiler, which is what POSIX requires; the GCC __attribute__ is used instead if it's available, however. in a few places, I've added infinite for loops at the end of _Noreturn functions to silence compiler warnings. presumably __buildin_unreachable could achieve the same thing, but it would only work on newer GCCs and would not be portable. the loops should have near-zero code size cost anyway. like the previous _Noreturn commit, this one is based on patches contributed by philomath. 2012-09-06 23:34:10 -04:00			`_Noreturn void __assert_fail(const char expr, const char file, int line, const char *func)`
initial check-in, version 0.5.0 2011-02-12 00:22:29 -05:00			`{`
			`fprintf(stderr, "Assertion failed: %s (%s: %s: %d)\n", expr, file, func, line);`
			`fflush(NULL);`
			`abort();`
			`}`