Debugger: Move part of engine startup to preparation phase

Change-Id: I414c356cd615096ee68588b839aaf975657fb7f9
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
This commit is contained in:
hjk
2017-04-27 15:39:30 +02:00
parent 009865f8b3
commit e213585910
6 changed files with 41 additions and 40 deletions

View File

@@ -201,6 +201,10 @@ public:
DebuggerRunParameters &runParameters();
virtual void setRunTool(DebuggerRunTool *runTool);
DebuggerRunTool *runTool() const;
void prepare();
void start();
void startDebugger();
enum {
@@ -340,19 +344,6 @@ public:
bool prepareCommand();
signals:
void stateChanged(Debugger::DebuggerState state);
/*
* For "external" clients of a debugger run control that needs to do
* further setup before the debugger is started (e.g. RemoteLinux).
* Afterwards, notifyEngineRemoteSetupFinished
* must be called to continue or abort debugging.
* This signal is only emitted if the start parameters indicate that
* a server start script should be used, but none is given.
*/
void requestRemoteSetup();
void aboutToNotifyInferiorSetupOk();
protected:
// The base notify*() function implementation should be sufficient
// in most cases, but engines are free to override them to do some