forked from qt-creator/qt-creator
Utils: Drop QProcess specific parameters from QtcProcess::finished()
Mid-term plan is to concentrate on use of QtcProcess::result() instead which is a bit more system-agnostic. There's quite a bit of potential for downstream cleanup by re-using QtcProcess::exitMessage() now. Change-Id: I3806b3f5933d96e64b7cfb18cc6c52823fddcbcd Reviewed-by: Christian Stenger <christian.stenger@qt.io>
This commit is contained in:
@@ -4085,12 +4085,12 @@ void GdbEngine::handleGdbError(QProcess::ProcessError error)
|
||||
}
|
||||
}
|
||||
|
||||
void GdbEngine::handleGdbFinished(int exitCode, QProcess::ExitStatus exitStatus)
|
||||
void GdbEngine::handleGdbFinished()
|
||||
{
|
||||
if (m_commandTimer.isActive())
|
||||
m_commandTimer.stop();
|
||||
|
||||
notifyDebuggerProcessFinished(exitCode, exitStatus, "GDB");
|
||||
notifyDebuggerProcessFinished(m_gdbProc.exitCode(), m_gdbProc.exitStatus(), "GDB");
|
||||
}
|
||||
|
||||
void GdbEngine::abortDebuggerProcess()
|
||||
|
||||
Reference in New Issue
Block a user