From 98cdd330609fb04ac40e88c48ae2fe85990b7283 Mon Sep 17 00:00:00 2001
From: hjk <qtc-committer@nokia.com>
Date: Thu, 29 Apr 2010 12:15:08 +0200
Subject: [PATCH] debugger: make error message after a broken stack response
less intrusive
---
src/plugins/debugger/gdb/classicgdbengine.cpp | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/src/plugins/debugger/gdb/classicgdbengine.cpp b/src/plugins/debugger/gdb/classicgdbengine.cpp
index 67f3a0d6f36..5bed94cc426 100644
--- a/src/plugins/debugger/gdb/classicgdbengine.cpp
+++ b/src/plugins/debugger/gdb/classicgdbengine.cpp
@@ -637,8 +637,9 @@ void GdbEngine::handleStackListArgumentsClassic(const GdbResponse &response)
const GdbMi args = frame.findChild("args");
m_currentFunctionArgs = args.children();
} else {
- qDebug() << "FIXME: GdbEngine::handleStackListArguments: should not happen"
- << response.toString();
+ // Seems to occur on "RedHat 4 based Linux" gdb 7.0.1:
+ // ^error,msg="Cannot access memory at address 0x0"
+ debugMessage(_("UNEXPECTED RESPONSE: ") + response.toString());
}
}
--
GitLab