Removed incorrect warning message from codagdbadapter

This commit is contained in:
Tom Sutcliffe
2011-03-09 16:00:18 +01:00
committed by Pawel Polanski
parent f567b2ed65
commit 11c9370143

View File

@@ -256,18 +256,8 @@ void CodaGdbAdapter::handleCodaRunControlModuleLoadContextSuspendedEvent(const C
m_session.codeseg = minfo.codeAddress;
m_session.dataseg = minfo.dataAddress;
logMessage(startMsg(m_session), LogMisc);
// 26.8.2010: When paging occurs in S^3, bogus starting ROM addresses
// like 0x500000 or 0x40000 are reported. Warn about symbol resolution
// errors. Code duplicated in TrkAdapter. @TODO: Hopefully fixed in
// future TRK versions.
if ((m_session.codeseg & 0xFFFFF) == 0) {
const QString warnMessage = tr("The reported code segment address "
"(0x%1) might be invalid. Symbol resolution or setting breakoints "
"may not work.").arg(m_session.codeseg, 0, 16);
logMessage(warnMessage, LogError);
}
const QByteArray symbolFile = m_symbolFile.toLocal8Bit();
const QByteArray symbolFile = m_symbolFile.toLocal8Bit();
if (symbolFile.isEmpty()) {
logMessage(_("WARNING: No symbol file available."), LogError);
} else {