Valgrind: Use generic timed future for uncertain progress

Change-Id: Idb7f1b1e5a0fcd0351d6c30f5a6dadcbec191898
Reviewed-by: Eike Ziller <eike.ziller@digia.com>

1 files changed, 0 insertions, 8 deletions

diff --git a/src/plugins/valgrind/callgrindengine.cpp b/src/plugins/valgrind/callgrindengine.cpp
index 08047f815b..9f9b703875 100644
--- a/src/plugins/valgrind/callgrindengine.cpp
+++ b/src/plugins/valgrind/callgrindengine.cpp
@@ -48,11 +48,8 @@ CallgrindRunControl::CallgrindRunControl(const AnalyzerStartParameters &sp,
     , m_markAsPaused(false)
 {
     connect(&m_runner, SIGNAL(finished()), this, SLOT(slotFinished()));
-    connect(&m_runner, SIGNAL(started()), this, SLOT(slotStarted()));
     connect(m_runner.parser(), SIGNAL(parserDataReady()), this, SLOT(slotFinished()));
     connect(&m_runner, SIGNAL(statusMessage(QString)), SLOT(showStatusMessage(QString)));
-
-    m_progress->setProgressRange(0, 2);
 }
 
 void CallgrindRunControl::showStatusMessage(const QString &msg)
@@ -157,8 +154,3 @@ void CallgrindRunControl::slotFinished()
 {
     emit parserDataReady(this);
 }
-
-void CallgrindRunControl::slotStarted()
-{
-    m_progress->setProgressValue(1);
-}