[Boost-bugs] [Boost C++ Libraries] #3664: SIGCHLD always considered fatal error

Subject: [Boost-bugs] [Boost C++ Libraries] #3664: SIGCHLD always considered fatal error
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2009-11-24 12:30:12

#3664: SIGCHLD always considered fatal error
 Reporter: Johan Nilsson <r DOT johan DOT nilsson AT gmail DOT com> | Owner: rogeeff
     Type: Bugs | Status: new
Milestone: Boost 1.42.0 | Component: test
  Version: Boost 1.40.0 | Severity: Problem
 Keywords: |
 Under *nix platforms, unless system error handling is disabled using e.g.
 "BOOST_TEST_CATCH_SYSTEM_ERRORS=no" in the environment, an exiting child
 process is always considered a fatal error, no matter what the reason for
 the child's exit is.

 Currently, the only way to disable this behaviour without simultaneously
 disable the handling of all system events is to recompile the library with
 the BOOST_TEST_IGNORE_SIGCHLD preprocessor macro defined. This makes it
 impossible to write tests that starts/stops child processes and attempts
 to inspect their exit codes using the vanilla build of Boost.Test.

 I suggest that the handling of SIGCHLD should be possible to
 enable/disable in the same way as the other run-time parameters, with a
 default value that disables handling of SIGCHLD (which is run-time
 compatible with older Boost releases).

 Some applicable references:


Ticket URL: <https://svn.boost.org/trac/boost/ticket/3664>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.

This archive was generated by hypermail 2.1.7 : 2017-02-16 18:50:01 UTC