diff options
author | hjk <qtc-committer@nokia.com> | 2010-04-29 12:15:08 +0200 |
---|---|---|
committer | hjk <qtc-committer@nokia.com> | 2010-04-29 12:15:08 +0200 |
commit | 98cdd330609fb04ac40e88c48ae2fe85990b7283 (patch) | |
tree | cb98d6fd4e1c515cc1788d96c617e06842688b27 /src | |
parent | 0205d1c3a6689560df1b1ccc55dc8a829675b107 (diff) | |
download | qt-creator-98cdd330609fb04ac40e88c48ae2fe85990b7283.tar.gz |
debugger: make error message after a broken stack response less intrusive
Diffstat (limited to 'src')
-rw-r--r-- | src/plugins/debugger/gdb/classicgdbengine.cpp | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/src/plugins/debugger/gdb/classicgdbengine.cpp b/src/plugins/debugger/gdb/classicgdbengine.cpp index 67f3a0d6f3..5bed94cc42 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()); } } |