Deal with SIGCHLD when using Boost.Process instead of not managing it at all.
Fixes some weird problems where unit tests or programs under a debugger would
misteriously fail due to an aborted waitpid(2) (because the testing framework
and the debugger reprogram this signal instead of simply ignoring it).
Our approach: reset the signal to its default behavior. Read the comments in
the detail/posix_sigchld.hpp file for more details on this.
(No files)
Note:
See TracChangeset
for help on using the changeset viewer.