+ We have not found the "outer" context on the stack.
+ Since it is not possible to reliably detect whether
+ we have a version of glibc (2.2.3+) that has the
+ context bugfix applied, or whether we have a version
+ of glibc that needs the scalpel code (2.2.2 and earlier),
+ or RedHat 7.1 (which is nominally 2.2.2 with internal 2.2.3
+ versioning) we cannot tell whether the modifications to
+ the "correct" context are enough to get exception handling
+ to work correctly.
+
+ If exception handling does not work due to the glibc context
+ confusion, it is likely that the process will hang dead on,
+ for instance, a SIGSEGV and not react at all to a SIGINT (Ctrl+C).
+
+ Because of this unpredictable behaviour take down the process hard.