From 4abc76811a74b45c8bab1bbe3add4b58b374a04b Mon Sep 17 00:00:00 2001 From: Matt Caswell Date: Fri, 9 Oct 2015 15:48:30 +0100 Subject: [PATCH] Fix Linux crash If config'd without -d (--debug), asynctest was crashing with: *** longjmp causes uninitialized stack frame *** This is because gcc will add certain checks for some functions (including longjmp). The checks assume you can only longjmp down the stack not up. However, if we are actually jumping to a different fibre then it can appear as if we are going up the stack when we are not really. This change disables the check. Reviewed-by: Rich Salz --- crypto/async/async.c | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/crypto/async/async.c b/crypto/async/async.c index 8fdff52d99..d08ac132b7 100644 --- a/crypto/async/async.c +++ b/crypto/async/async.c @@ -51,6 +51,14 @@ * ==================================================================== */ +/* + * Without this we start getting longjmp crashes because it thinks we're jumping + * up the stack when in fact we are jumping to an entirely different stack. The + * cost of this is not having certain buffer overrun/underrun checks etc for + * this source file :-( + */ +#undef _FORTIFY_SOURCE + #include #include #include -- GitLab