ee068f2ec5
We were accidentally closing it along with all the other file descriptors if the CloseFileDescriptors flag was active. That meant we were unable to report start problems back to the parent process. So instead of closing everything immediately, we simply mark everything as FD_CLOEXEC so they'll be closed by execve()'s success. Because we're using CLOSE_RANGE_CLOEXEC now to detect the system call, we don't need the configure-time test. [ChangeLog][QtCore][QProcess] Fixed a bug that caused QProcess not to report start failures if the UnixProcessFlag::CloseFileDescriptors flag was active. Change-Id: I4d81d763281354e886d9fffd56ef6ab8b6115715 Reviewed-by: Alexey Edelev <alexey.edelev@qt.io> Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io> Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@gmx.de> (cherry picked from commit 3d007ff2e9caf328f92d65f71a94fd869552b1b6) (cherry picked from commit 01010851cb61f5d7964ba2317defb67cdfcb72f5) |
||
|---|---|---|
| .. | ||
| auto | ||
| baseline | ||
| benchmarks | ||
| global | ||
| libfuzzer | ||
| manual | ||
| shared | ||
| testserver | ||
| CMakeLists.txt | ||
| README | ||
README
This directory contains autotests and benchmarks based on Qt Test. In order
to run the autotests reliably, you need to configure a desktop to match the
test environment that these tests are written for.
Linux X11:
* The user must be logged in to an active desktop; you can't run the
autotests without a valid DISPLAY that allows X11 connections.
* The tests are run against a KDE3 or KDE4 desktop.
* Window manager uses "click to focus", and not "focus follows mouse". Many
tests move the mouse cursor around and expect this to not affect focus
and activation.
* Disable "click to activate", i.e., when a window is opened, the window
manager should automatically activate it (give it input focus) and not
wait for the user to click the window.