From 9539f527fcda6ca9b8df09e63fd93f0206649a41 Mon Sep 17 00:00:00 2001 From: Thiago Macieira Date: Tue, 16 Jan 2024 07:50:45 -0800 Subject: [PATCH] QProcess/Doc: remove the note that about FailedToStart after started() It was added in commit 75a2c81b0041df4ca59178cf52d9e5a8815f3524: Handle posix_spawn using exit code 127 to indicate fail-to-start Most posix_spawn implementations are done using fork(), so the only way to report errors afer fork() is via a special exit code. Support for posix_spawn was removed when we dropped QNX 6.5 support in Qt 5.7 (commit 005a8bfbf0022f03dafafcf2b5c438ccf0675a49). Also complements commit d012e953bfb498091c0ea9a83a717a3deffc670f. Pick-to: 6.6 Change-Id: I76ffba14ece04f24b43efffd17aadead7c30146b Reviewed-by: Oswald Buddenhagen Reviewed-by: Ahmad Samir (cherry picked from commit 75254e1d355b2eb33fece8bc1a468ce92ac65c7e) Reviewed-by: Qt Cherry-pick Bot --- src/corelib/io/qprocess.cpp | 3 --- 1 file changed, 3 deletions(-) diff --git a/src/corelib/io/qprocess.cpp b/src/corelib/io/qprocess.cpp index 5f37e47944d..59b8b79e05c 100644 --- a/src/corelib/io/qprocess.cpp +++ b/src/corelib/io/qprocess.cpp @@ -1997,9 +1997,6 @@ QProcessEnvironment QProcess::processEnvironment() const If msecs is -1, this function will not time out. - \note On some UNIX operating systems, this function may return true but - the process may later report a QProcess::FailedToStart error. - \sa started(), waitForReadyRead(), waitForBytesWritten(), waitForFinished() */ bool QProcess::waitForStarted(int msecs)