674e79416f
The rule for a new override is that it must still work if the old implementation is called. The catch is that any class that derives from QProcess and isn't recompiled will still have QIODevice::open in its virtual table. That is equivalent to overriding open() and calling QIODevice::open() (like the tests). In Qt 5.0, QProcess::start() called QIODevice::open directly, not the virtual open(), so there's no expectation that a user-overridden open() be called. With that in mind, simply fix QProcess::start to not call the virtual open at all. Similarly with QLocalSocket, the calls to open were always non-virtual. Task-number: QTBUG-32284 Change-Id: I88925f0ba08bc23c849658b54582744997e69a4c Reviewed-by: Giuseppe D'Angelo <giuseppe.dangelo@kdab.com> |
||
---|---|---|
.. | ||
fileWriterProcess | ||
test | ||
testBatFiles | ||
testDetached | ||
testExitCodes | ||
testForwarding | ||
testGuiProcess | ||
testProcessCrash | ||
testProcessDeadWhileReading | ||
testProcessEcho | ||
testProcessEcho2 | ||
testProcessEcho3 | ||
testProcessEchoGui | ||
testProcessEnvironment | ||
testProcessEOF | ||
testProcessNormal | ||
testProcessOutput | ||
testProcessSpacesArgs | ||
testSetWorkingDirectory | ||
testSoftExit | ||
testSpaceInName | ||
.gitignore | ||
qprocess.pri | ||
qprocess.pro | ||
tst_qprocess.cpp |