forked from qt-creator/qt-creator
Debugger: Properly exit when engine run failed
Instantly stop the engine if e.g. the port is blocked. If we let it running until the user closes the dialog, the timeout for automatic connects would be triggered, and we'd get yet another dialog afterwards telling the user that the connection failed. Change-Id: Ifd0e9d743f3b8f4ba853be032d9527559ef6004e Reviewed-by: Aurindam Jana <aurindam.jana@nokia.com>
This commit is contained in:
@@ -163,7 +163,8 @@ signals:
|
||||
private slots:
|
||||
void beginConnection(quint16 port = 0);
|
||||
void connectionEstablished();
|
||||
void connectionStartupFailed(const QString &errorMessage = QString());
|
||||
void connectionStartupFailed();
|
||||
void appStartupFailed(const QString &errorMessage);
|
||||
void connectionError(QAbstractSocket::SocketError error);
|
||||
void serviceConnectionError(const QString &service);
|
||||
void appendMessage(const QString &msg, Utils::OutputFormat);
|
||||
|
||||
Reference in New Issue
Block a user