forked from qt-creator/qt-creator
process synchrounus process output in every case
there is no logical difference between a hung or crashed process and one that exited non-zero. blocking execution already behaved that way. Change-Id: Ifb80d050f9771cb9ea4021329ffef8e646e43ac9 Reviewed-by: Orgad Shaneh <orgads@gmail.com>
This commit is contained in:
@@ -495,10 +495,8 @@ SynchronousProcessResponse SynchronousProcess::run(const CommandLine &cmd,
|
||||
if (isGuiThread())
|
||||
QApplication::setOverrideCursor(Qt::WaitCursor);
|
||||
d->m_eventLoop.exec(QEventLoop::ExcludeUserInputEvents);
|
||||
if (d->m_result.result == SynchronousProcessResponse::Finished || d->m_result.result == SynchronousProcessResponse::FinishedError) {
|
||||
processStdOut(false);
|
||||
processStdErr(false);
|
||||
}
|
||||
processStdOut(false);
|
||||
processStdErr(false);
|
||||
|
||||
d->m_result.rawStdOut = d->m_stdOut.rawData;
|
||||
d->m_result.rawStdErr = d->m_stdErr.rawData;
|
||||
|
Reference in New Issue
Block a user