Bug 71691

Summary: Viewers in debugger could use a better UI
Product: [Applications] kdevelop Reporter: Jon Smirl <jonsmirl>
Component: CPP DebuggerAssignee: kdevelop-bugs-null
Status: RESOLVED UNMAINTAINED    
Severity: wishlist CC: niko.sams
Priority: NOR    
Version: 4.0.0   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:

Description Jon Smirl 2004-01-02 19:35:07 UTC 
Version:           CVS (using KDE Devel)

The debugger viewer dialog probably isn't needed. It would be much more convenient if the memory and register viewers were made into tree tool views. The libraries would be an output tool view. Disassembly is already an output tool view.

The advantage to this is that you could single step the debugger and watch the output views. It would also simplify the UI somewhat. The tabs for these viewers would only appear when the debugger is active.

Another excellent addition would be to mix the source lines into the disassembly display.

Right now the inability to keep the registers displayed while single stepping makes kdevelop unusable for assembly work.
Comment 1 Gunther Piez 2005-08-30 19:27:25 UTC 
I second that.

The "Views" for the Debugger are completly useless, since you can't step while a view is active.
The Disassembly window has some issues too, it can't scroll back and often not enough lines are displayed. Something like the source window in kdbg (which I am actually using when it comes to debugging) would be nice.
Value and type of a variable could be displayed as a tool tip ond mouseover.
Comment 2 Krystof Zacek 2006-04-06 11:59:06 UTC 
I absolutely agree. The debug viewers must be available as a non-modal docked window, analogically to watch window, otherwise it is pretty useless.

The memory dump should be done like in Visual Studio:  docked, the memory changes are visible in different color while stepping through the code, I can select the format (1,2 or 4 bytes), and there should definitelly be an ASCII stripe to see text. It also should be possible to change the memory contents here manually. In fact, all this should closely resemble KHexedit.

The memory dump should display memory from the given base up to the dock display size (currently one has to enter both base and size).

Is there any progress on this?
Comment 3 Niko Sams 2009-07-26 22:17:46 UTC 
KDevelop4 has all views docked. The debugger creates no dialogs afaik.