Re: [Boost-users] [test] Still SIGCHLD issues?

Subject: Re: [Boost-users] [test] Still SIGCHLD issues?
From: Boris Schaeling (boris_at_[hidden])
Date: 2009-11-05 05:44:57

On Thu, 05 Nov 2009 09:06:16 +0100, Johan Nilsson  
<r.johan.nilsson_at_[hidden]> wrote:

> [...]
>> You can define BOOST_TEST_IGNORE_NON_ZERO_CHILD_CODE or
>> BOOST_TEST_IGNORE_SIGCHLD for Boost.Test which as far as I remember
>> must be rebuilt then. :-/
>
> Thanks for the pointer. I was hoping for a provided run-time solution,  
> which would have been the best.

Yes, I agree.

> 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.

It's the execution monitor in file /boost/test/impl/execution_monitor.ipp  
which registers the signal handlers. The execution monitor has a public  
property called p_catch_system_errors which (according to  
http://www.boost.org/doc/libs/1_40_0/libs/test/doc/html/execution-monitor/user-guide.html)  
can be set to false to suppress registering any signal handler. It's all  
or nothing but there seems to be a way.

Boris