16 Nov
2009
16 Nov
'09
4:32 p.m.
Boris Schaeling
Thanks for the pointer. I was hoping for a provided run-time solution, which would have been the best.
Yes, I agree.
If nothing else works, you can reset signal handler yourself inside the test case.
If stuck with a compile-time solution, it would IMHO have been more lenient having to define e.g. BOOST_TEST_HANDLE_NON_ZERO_CHILD_CODE and BOOST_TEST_HANDLE_SIGCHLD rather than having this new behaviour by default. I really can't currently imagine a scenario where I would want this enabled.
Boost.Test is trying to catch all kinds of failures. Child proces crashing or returning non-zero error code is usual indication of an error. Gennadiy.