Debugger: Use QElapsedTimer instead of QTime::elapsed()

Deprecation looming.

Change-Id: Ibafbac6fbe48d74ba7d88c22400d581e49e4e45d
Reviewed-by: David Schulz <david.schulz@qt.io>
Reviewed-by: Edward Welbourne <edward.welbourne@qt.io>
This commit is contained in:
hjk
2019-06-12 12:23:48 +02:00
parent 2391ef6088
commit 07f50c8dec
2 changed files with 7 additions and 11 deletions

View File

@@ -324,12 +324,9 @@ static QStringList mergeEnvironment(QStringList runConfigEnvironment,
return runConfigEnvironment;
}
int CdbEngine::elapsedLogTime() const
int CdbEngine::elapsedLogTime()
{
const int elapsed = m_logTime.elapsed();
const int delta = elapsed - m_elapsedLogTime;
m_elapsedLogTime = elapsed;
return delta;
return m_logTimer.restart();
}
void CdbEngine::createFullBacktrace()
@@ -352,8 +349,8 @@ void CdbEngine::setupEngine()
qDebug(">setupEngine");
init();
if (!m_logTime.elapsed())
m_logTime.start();
if (!m_logTimer.elapsed())
m_logTimer.start();
// Console: Launch the stub with the suspended application and attach to it
// CDB in theory has a command line option '-2' that launches a