Version: 3.3.2 (using KDE 3.5.2, Kubuntu Package 4:3.5.2-0ubuntu1 dapper) Compiler: Target: i486-linux-gnu OS: Linux (i686) release 2.6.15-20-386 It wasn't obvious to me when debugging and no source is available what's happening, the only indication is on the status line and it's not that prominent. I think the Disassemble window should be shown by default to show that it's tracing into code with no source. This would make it obvious and also allow people to see that they could step out.
*** Bug 289992 has been marked as a duplicate of this bug. ***
*** Bug 290992 has been marked as a duplicate of this bug. ***
My plan to fix this issue: skip lines in framestack that have no file/linenumber associated. I think showing a disassemble window would make clear what happens, but would be of no real value - as you usually debug only code where you have debug symbols available.
Git commit 7a6f264beb45e4a449527cb571539cc49e156ef1 by Niko Sams. Committed on 11/03/2012 at 18:25. Pushed by nsams into branch 'master'. when frames don't contain filename and linenumber skip them and set the first with debug info as current this happens when stopping inside a library without debug symbols M +11 -0 debugger/framestack/framestackmodel.cpp M +0 -1 debugger/interfaces/ivariablecontroller.cpp http://commits.kde.org/kdevplatform/7a6f264beb45e4a449527cb571539cc49e156ef1
Git commit b9199cea5837d84b7f78c41de0ea65226c022cc1 by Niko Sams. Committed on 11/03/2012 at 18:29. Pushed by nsams into branch 'master'. add test for latest platform change (7a6f264beb45e4a449527cb571539cc49e156ef1) M +3 -0 debuggers/gdb/unittests/CMakeLists.txt A +37 -0 debuggers/gdb/unittests/debugeeexception.cpp [License: LGPL (v2)] M +38 -1 debuggers/gdb/unittests/gdbtest.cpp M +1 -0 debuggers/gdb/unittests/gdbtest.h http://commits.kde.org/kdevelop/b9199cea5837d84b7f78c41de0ea65226c022cc1