Valgrind: Refactor Parser

Make it implicitly threaded.

Get rid of ThreadedParser.

Don't move QTcpSocket instances, received by
QTcpServer::nextPendingConnection(), into another thread,
as docs says it's not safe.

Use wait condition for waiting for new data.

Don't potentially leak the Parser in loadXmlLogFile():
store a unique pointer to the running parser.

Introduce Parser::setData() method and use it with
QFile device in loadXmlLogFile().

Pass QAbstractSocket into the parser instead of
QIODevice and get rid of downcasting. The QIODevice
couldn't really work with non-socket and non-file devices
(like e.g. QProcess), as it lacks general error and finished
reporting signals (it has only general readyRead() signal).

Change-Id: I9352aec694564d4d2a26898841ed964bed470d82
Reviewed-by: <[email protected]>
Reviewed-by: hjk <[email protected]>

1 files changed, 0 insertions, 1 deletions

diff --git a/src/plugins/valgrind/valgrind.qbs b/src/plugins/valgrind/valgrind.qbs
index 378f0a57bb8..065006352e3 100644
--- a/src/plugins/valgrind/valgrind.qbs
+++ b/src/plugins/valgrind/valgrind.qbs
@@ -69,7 +69,6 @@ QtcPlugin {
             "stackmodel.cpp", "stackmodel.h",
             "status.cpp", "status.h",
             "suppression.cpp", "suppression.h",
-            "threadedparser.cpp", "threadedparser.h",
         ]
     }