Debugger: Move server into it's own thread

So far the debugger infrastructure was running in the GUI thread,
which required e.g. nested event loops to implement blocking behavior.
The server and networking code are now running in their own thread,
while the services are still running in the main thread.

Because v8 isn't thread safe, we're adding two new JSEngines + isolates
to qv8debugservice: One to decode JSON messages in the debugger thread,
and one in the GUI thread.

Change-Id: I746f5e203968f7bcc510fb66118c88ef0fd0cd14
Reviewed-by: Christiaan Janssen <christiaan.janssen@nokia.com>

1 files changed, 4 insertions, 2 deletions

diff --git a/src/declarative/debugger/qv8debugservice_p.h b/src/declarative/debugger/qv8debugservice_p.h
index d8101ae3ff..9785bb9849 100644
--- a/src/declarative/debugger/qv8debugservice_p.h
+++ b/src/declarative/debugger/qv8debugservice_p.h
@@ -76,13 +76,15 @@ public:
     void addEngine(QDeclarativeEngine *);
     void removeEngine(QDeclarativeEngine *);
 
-    void debugMessageHandler(const QString &message);
-    void executionStopped();
+    void debugMessageHandler(const QString &message, bool willStartRunning);
 
     void appendSourcePath(const QString &message);
 
     void signalEmitted(const QString &signal);
 
+private slots:
+    void scheduledDebugBreak();
+
 protected:
     void messageReceived(const QByteArray &);