feedc0de/qt-creator
1
0
Fork 0
forked from qt-creator/qt-creator
Code Pull Requests Activity

debugger: remove inferiorStarted() signal.

Browse Source 
It had unclear semantics and was only used to show a statusmessage.
We do that directly now.
This commit is contained in:
hjk
2009-09-29 10:15:52 +02:00
parent f685aa2361
commit 10fa3b2b76
9 changed files with 24 additions and 33 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
src/plugins/debugger/gdb/trkgdbadapter.cpp
View File

@@ -1463,15 +1463,14 @@ void TrkGdbAdapter::startInferior()
QTC_ASSERT(state() == InferiorStarting, qDebug() << state());
setState(InferiorRunningRequested);
m_engine->postCommand(_("-exec-continue"), CB(handleFirstContinue));
// FIXME: Is there a way to properly recognize a successful start?
emit inferiorStarted();
}
void TrkGdbAdapter::handleFirstContinue(const GdbResponse &record)
{
QTC_ASSERT(state() == InferiorRunningRequested, qDebug() << state());
if (record.resultClass == GdbResultDone) {
// inferiorStarted already emitted above, see FIXME
debugMessage(_("INFERIOR STARTED"));
showStatusMessage(tr("Inferior running."));
} else if (record.resultClass == GdbResultError) {
//QString msg = __(record.data.findChild("msg").data());
QString msg1 = tr("Connecting to remote server failed:");