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

debugger: add some possible explanation for the need to ask for stacktraces twice

Browse Source
This commit is contained in:
hjk
2009-09-16 11:46:15 +02:00
parent 14b081f700
commit b96b2a2b3a
1 changed files with 6 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
src/plugins/debugger/gdb/gdbengine.cpp
View File

@@ -1283,7 +1283,12 @@ void GdbEngine::reloadStack()
if (stackDepth && !m_gdbAdapter->isAdapter())
cmd += _(" 0 ") + QString::number(stackDepth);
postCommand(cmd, WatchUpdate, CB(handleStackListFrames), false);
// FIXME: gdb 6.4 likes to be asked twice
// FIXME: gdb 6.4 symbianelf likes to be asked twice. The first time it
// returns with "^error,msg="Previous frame identical to this frame
// (corrupt stack?)". Might be related to the fact that we can't
// access the memory belonging to the lower frames. But as we know
// this always happens, ask the second time immediately instead
// of waiting for the first request to fail.
if (m_gdbAdapter->isAdapter())
postCommand(cmd, WatchUpdate, CB(handleStackListFrames), false);
}