catch3/include/internal/catch_debugger.h, branch v2.2.2 Progmasoft Catch3: an independently maintained C++17 test framework with a parallel runner, property checks, snapshots and structured results. Fixes for cygwin 2018-02-01T16:14:20+00:00 philsquared 2018-02-01T16:14:12+00:00 5713381d060e94647d110227e2943c0aa9951401 






Remove isTrue, alwaysTrue, alwaysFalse
2017-11-22T15:03:45+00:00

Martin Hořeňovský

2017-11-21T20:39:40+00:00

401ad7a18941fb3744533a315a8a9500a7f573c9

isTrue and alwaysFalse were replaced by (void)0, 0 inspired by doctest
alwaysTrue was replaced by warning suppression





isTrue and alwaysFalse were replaced by (void)0, 0 inspired by doctest
alwaysTrue was replaced by warning suppression







Split writeToDebugConsole out of main path
2017-08-29T11:51:55+00:00

Martin Hořeňovský

2017-08-29T11:51:55+00:00

5932576f534ef08a3d13b0cd99464999dbe7b50b












Suppress clang-tidy warnings about inline asm
2017-07-13T07:26:08+00:00

Phil Nash

2017-07-13T07:26:08+00:00

d2d591047995b80bb9e55d104397c229a586d644












Removed debug break support for PowerPC Macs
2017-04-25T11:27:26+00:00

Phil Nash

2017-04-25T11:27:26+00:00

5c8ea03cc85a750d4d8fdd9da1ef02f645a17cac












Enable breaking into debugger on Mac
2017-01-31T16:00:42+00:00

Josef Kemetmueller

2017-01-23T20:19:10+00:00

70d3c937c31bfa28fbba940d505b6de006ea8529

The integrated assembler segment was missing an underscore:
"_asm__". Also we remove the "DEBUG" macro check, so we are consistent
with the linux and windows variant.
Now breaking into gdb on failure should work via:
	gdb --args test_executable --break





The integrated assembler segment was missing an underscore:
"_asm__". Also we remove the "DEBUG" macro check, so we are consistent
with the linux and windows variant.
Now breaking into gdb on failure should work via:
	gdb --args test_executable --break







Use inline assembly with gcc under Linux for CATCH_TRAP
2017-01-15T18:29:34+00:00

Vadim Zeitlin

2016-02-05T14:09:16+00:00

e1c4a4bd9b4507c86643ac825deb61da047f53e1

This is more convenient than using the generic portable raise(SIGTRAP) as it
avoids having another stack frame in the debugger when the break happens.





This is more convenient than using the generic portable raise(SIGTRAP) as it
avoids having another stack frame in the debugger when the break happens.







Refactor CATCH_BREAK_INTO_DEBUGGER() to avoid repetition
2017-01-15T18:29:34+00:00

Vadim Zeitlin

2016-02-05T14:08:16+00:00

25d017763b73e09d3e9adf7f4db9ce71992f0471

Don't duplicate Catch::isDebuggerActive() check many times, do it just once
in CATCH_BREAK_INTO_DEBUGGER() definition and use a separate CATCH_TRAP()
macro for the really platform-dependent part.





Don't duplicate Catch::isDebuggerActive() check many times, do it just once
in CATCH_BREAK_INTO_DEBUGGER() definition and use a separate CATCH_TRAP()
macro for the really platform-dependent part.







Add support for breaking into debugger for Linux
2017-01-15T18:29:34+00:00

Vadim Zeitlin

2016-02-05T13:56:20+00:00

b634e592dac83edddf724c2e243c674132ddfa8c

Use Linux-specific /proc/$PID/status file to check whether we're being
debugged and a generic raise(SIGTRAP) to actually break into the debugger.





Use Linux-specific /proc/$PID/status file to check whether we're being
debugged and a generic raise(SIGTRAP) to actually break into the debugger.







Big assertion capture refactoring.
2014-05-28T17:53:01+00:00

Phil Nash

2014-05-28T17:53:01+00:00

9438a03d5b564de23c379c93bd2c7aa1e7cbb010

- moved as much logic out of the macros as possible
- moved most logic into new ResultBuilder class, which wraps ExpressionResultBuilder (may take it over next), subsumes ResultAction and also takes place of ExpressionDecomposer.

This introduces many SRP violations - but all in the name of minimising macro logic!





- moved as much logic out of the macros as possible
- moved most logic into new ResultBuilder class, which wraps ExpressionResultBuilder (may take it over next), subsumes ResultAction and also takes place of ExpressionDecomposer.

This introduces many SRP violations - but all in the name of minimising macro logic!