trk: work around stack trace problems

Asking gdb twice seems to work.

trk: work around stack trace problems
Asking gdb twice seems to work.
61eadde6 · hjk · 1066dad5 · 61eadde6
Commit 61eadde6 authored Sep 16, 2009 by hjk
Hide whitespace changes
Inline Side-by-side

Showing with 3 additions and 0 deletions

src/plugins/debugger/gdb/gdbengine.cpp src/plugins/debugger/gdb/gdbengine.cpp +3 -0

No files found.
--- a/src/plugins/debugger/gdb/gdbengine.cpp
+++ b/src/plugins/debugger/gdb/gdbengine.cpp
@@ -1283,6 +1283,9 @@ 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
+    if (m_gdbAdapter->isAdapter())
+        postCommand(cmd, WatchUpdate, CB(handleStackListFrames), false);
 }

 void GdbEngine::handleAsyncOutput2(const GdbResultRecord &, const QVariant &cookie)