forked from qt-creator/qt-creator
QtcProcess: Fix stdErr() assert
The keepRawData field may be false only after calling
setStdErrLineCallback(). In all current usages (7 places)
we don't call stdErr() nor cleanedStdErr().
VcsCommand was using setStdErrCallback() so that did not
change the keepRawData to false.
It looks like currently it should be safe to fix this assert.
Amends 4000819262
Change-Id: I9f8627166d194579c5a0fe13d241ff37aecac47c
Reviewed-by: hjk <hjk@qt.io>
This commit is contained in:
@@ -1688,11 +1688,7 @@ QString QtcProcess::stdOut() const
|
||||
|
||||
QString QtcProcess::stdErr() const
|
||||
{
|
||||
// FIXME: The tighter check below is actually good theoretically, but currently
|
||||
// VcsCommand::runFullySynchronous triggers it and disentangling there
|
||||
// is not trivial. So weaken it a bit for now.
|
||||
//QTC_CHECK(d->m_stdErr.keepRawData);
|
||||
QTC_CHECK(d->m_stdErr.keepRawData || d->m_stdErr.rawData.isEmpty());
|
||||
QTC_CHECK(d->m_stdErr.keepRawData);
|
||||
return d->m_codec->toUnicode(d->m_stdErr.rawData);
|
||||
}
|
||||
|
||||
|
||||
Reference in New Issue
Block a user