From 2c1f8fd5da3306fd7c8a2267467e44eb61f12dd4 Mon Sep 17 00:00:00 2001 From: rofl0r Date: Tue, 1 Jan 2013 07:59:11 +0100 Subject: __assert_fail(): remove _Noreturn, to get proper stacktraces for _Noreturn functions, gcc generates code that trashes the stack frame, and so it makes it impossible to inspect the causes of an assert error in gdb. abort() is not affected (i have not yet investigated why). --- include/assert.h | 2 +- src/exit/assert.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/include/assert.h b/include/assert.h index c64d3e52..ab745db1 100644 --- a/include/assert.h +++ b/include/assert.h @@ -12,7 +12,7 @@ extern "C" { #endif -_Noreturn void __assert_fail (const char *, const char *, int, const char *); +void __assert_fail (const char *, const char *, int, const char *); #ifdef __cplusplus } diff --git a/src/exit/assert.c b/src/exit/assert.c index 49b0dc3e..e87442a7 100644 --- a/src/exit/assert.c +++ b/src/exit/assert.c @@ -1,7 +1,7 @@ #include #include -_Noreturn void __assert_fail(const char *expr, const char *file, int line, const char *func) +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); -- cgit v1.2.1