QProcess::startDetached/Unix: fix the resetting of SIGPIPE

This should have been SIG_DFL, as we're about to execute a child
process. It's the child's responsibility to ignore SIGPIPE if it wants
to, or get killed by it when it writes to an pipe with no readers.

Qt itself does this for its own purposes (see qt_ignore_sigpipe() [until
I can get some time to teach Linux about O_NOSIGPIPE]). Therefore, we
ought to reset what we've done.

Change-Id: Ic90d8429a0eb4837971dfffd166585a686790dde
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@gmx.de>
(cherry picked from commit f4e3b073b3d2a50133d734dd604bff21f061a3e6)

1 files changed, 1 insertions, 5 deletions

diff --git a/src/corelib/io/qprocess_unix.cpp b/src/corelib/io/qprocess_unix.cpp
index 8c6a095844..f235ab1320 100644
--- a/src/corelib/io/qprocess_unix.cpp
+++ b/src/corelib/io/qprocess_unix.cpp
@@ -911,11 +911,7 @@ bool QProcessPrivate::startDetached(qint64 *pid)
 
     pid_t childPid = fork();
     if (childPid == 0) {
-        struct sigaction noaction;
-        memset(&noaction, 0, sizeof(noaction));
-        noaction.sa_handler = SIG_IGN;
-        ::sigaction(SIGPIPE, &noaction, nullptr);
-
+        ::signal(SIGPIPE, SIG_DFL);     // reset the signal that we ignored
         ::setsid();
 
         qt_safe_close(startedPipe[0]);