Version: CVS (using KDE Devel) Installed from: Compiled sources I just hit a fault in some asm code. kdevelop stop and the debugger works just fine. But in the disassembly window the disassembly starts at the faulting instruction and proceeds forward. This isn't very useful. I need to see the instruction before I hit the fault to know what caused the fault. You aren't able to scroll backwards from the point of the fault. A fix might be to have gdb start disassembling from the start of the subroutine and then match the point of the fault up to that listing. A bonus wish would be to intermix the C source code lines with the disassembly lines. Does gcc/gdb provide line number offsets in it's debug data? If so it is easy to mix the source lines into the disassembly window.
There's not even support for disassembly currently and won't be for the first release. Please re-open if KDevelop4 gains disassembly support again.