forked from qt-creator/qt-creator
Debugger: Streamline ramping down
There were only two used target states, and in case of mixed debugging all parts of the machinery better agree on the direction. So one bool in the (shared) runTool is sufficient. Change-Id: Iffbf1651b82dde707cfc37d8da9d3da573b34b76 Reviewed-by: Christian Stenger <christian.stenger@qt.io>
This commit is contained in:
@@ -838,7 +838,7 @@ void CdbEngine::shutdownEngine()
|
||||
|
||||
void CdbEngine::abortDebugger()
|
||||
{
|
||||
if (targetState() == DebuggerFinished) {
|
||||
if (isDying()) {
|
||||
// We already tried. Try harder.
|
||||
showMessage("ABORTING DEBUGGER. SECOND TIME.");
|
||||
m_process.kill();
|
||||
@@ -1834,7 +1834,7 @@ unsigned CdbEngine::examineStopReason(const GdbMi &stopReason,
|
||||
{
|
||||
// Report stop reason (GDBMI)
|
||||
unsigned rc = 0;
|
||||
if (targetState() == DebuggerFinished)
|
||||
if (isDying())
|
||||
rc |= StopShutdownInProgress;
|
||||
if (debug)
|
||||
qDebug("%s", qPrintable(stopReason.toString(true, 4)));
|
||||
|
||||
Reference in New Issue
Block a user