catch3/src/catch2/internal/catch_fatal_condition_handler.hpp, branch remove_redundant_destructors Progmasoft Catch3: an independently maintained C++17 test framework with a parallel runner, property checks, snapshots and structured results. Cleanup includes in sources 2023-12-23T10:23:32+00:00 Martin Hořeňovský 2023-12-21T17:42:40+00:00 9aadc3a53d7208f8b44260dfef26b18671f7edd0 Mainly just removes some unused includes, but sometimes the include is replaced by a smaller header instead. 
Mainly just removes some unused includes, but sometimes the include
is replaced by a smaller header instead.
Fix references to license file 2022-10-28T09:30:15+00:00 Lars Toenning 2022-10-28T09:22:53+00:00 f1084fb30990fe40c8f5b70034970c7eb4e1da72 The license file was renamed with 6a502cc2f5fedd59b3495b58708f0d6d987ed9e1 
The license file was renamed with 6a502cc2f5fedd59b3495b58708f0d6d987ed9e1
Fix disengage failure logs for FatalConditionHandlerGuard 2022-03-24T14:49:02+00:00 Kochetkov, Yuriy 2022-02-08T10:43:40+00:00 2ce64d1d8f265bba48f3b7bb2130d0cfbfb51ed4 FatalConditionHandlerGuard is used within RunContext::invokeActiveTestCase(). The intent of this guard is to avoid binary crash without failed test being reported. Still in case FatalConditionHandlerGuard destructor being called during stack unwinding AND finds unexpected top-level filter for SEH unhandled exception, the binary may still crash. As result of such crash the original exception details are being hidden. As the Catch2 provides only `CATCH_CATCH_ANON` macro, with no access to exception details by design, looks like the best way to handle issue is to: - state requirements explicitly by `noexcept` specifier - use `Catch::cerr()` to print out possible issue notification Signed-off-by: Kochetkov, Yuriy <yuriyx.kochetkov@intel.com> 
FatalConditionHandlerGuard is used within RunContext::invokeActiveTestCase().
The intent of this guard is to avoid binary crash without failed test being
reported.
Still in case FatalConditionHandlerGuard destructor being called during stack
unwinding AND finds unexpected top-level filter for SEH unhandled exception,
the binary may still crash. As result of such crash the original exception
details are being hidden.

As the Catch2 provides only `CATCH_CATCH_ANON` macro, with no access to
exception details by design, looks like the best way to handle issue is to:
 - state requirements explicitly by `noexcept` specifier
 - use `Catch::cerr()` to print out possible issue notification

Signed-off-by: Kochetkov, Yuriy <yuriyx.kochetkov@intel.com>
Significantly refactor fatal error handling 2021-05-09T21:34:15+00:00 Martin Hořeňovský 2021-03-27T16:54:22+00:00 c0d0a50bdb2ae2f749443c0386c2b25379bdbf76 Because new glibc has changed `MINSIGSTKSZ` to be a syscall instead of being constant, the signal posix handling needed changes, as it used the value in constexpr context, for deciding size of an array. It would be simple to fix it by having the handler determine the signal handling stack size and allocate the memory every time the handler is being installed, but that would add another allocation and a syscall every time a test case is entered. Instead, I split apart the idea of preparing fatal error handlers, and engaging them, so that the memory can be allocated only once and still be guarded by RAII. Also turns out that Catch2's use of `MINSIGSTKSZ` was wrong, and we should've been using `SIGSTKSZ` the whole time, which we use now. Closes #2178 
Because new glibc has changed `MINSIGSTKSZ` to be a syscall instead
of being constant, the signal posix handling needed changes, as it
used the value in constexpr context, for deciding size of an array.
It would be simple to fix it by having the handler determine the
signal handling stack size and allocate the memory every time the
handler is being installed, but that would add another allocation
and a syscall every time a test case is entered.

Instead, I split apart the idea of preparing fatal error handlers,
and engaging them, so that the memory can be allocated only once
and still be guarded by RAII.

Also turns out that Catch2's use of `MINSIGSTKSZ` was wrong, and
we should've been using `SIGSTKSZ` the whole time, which we use now.

Closes #2178
Add standardized copyright notice + SPDX identifier to source files 2020-08-30T13:43:45+00:00 Martin Hořeňovský 2020-08-30T13:43:45+00:00 90aeffb97d6942d16f75a56b11e10fc0b010995a This should also be done for test files, but that has lower priority. 
This should also be done for test files, but that has lower priority.
Standardize include guard patterns to FILE_NAME_EXTENSION_INCLUDED 2020-08-30T12:09:27+00:00 Martin Hořeňovský 2020-08-29T18:48:32+00:00 a822cb9717b64b3b17047fe1ab4dc727c2ff39c4 This commit also strips the old copyright comment header in touched files, as those will also be replaced with a more standardized and machine-friendly version. 
This commit also strips the old copyright comment header in touched
files, as those will also be replaced with a more standardized and
machine-friendly version.
Small cleanup of fatal condition handler 2020-04-25T12:07:50+00:00 Martin Hořeňovský 2020-04-25T12:07:50+00:00 517839fb3f7f0fd7823dadce69ab791628d1bc27