Slow stepping

[Nick Savoiu]

I agree. There has been some improvement lately (probably from not retrieving the entire frame stack) but it's still fairly far from responsive. 

I vote for the second option (delay retrieval by some user specified time) as I sometimes find myself needing to quickly step over a few lines of code before I get to the interesting stuff again. I know "jump to cursor is there" but it involves switching from the keyboard to the mouse.

Nick

----- Original Message ----
From: Andras Mantia <amantia at kde.org>
To: kdevelop-devel at kdevelop.org
Sent: Sunday, January 14, 2007 12:23:05 AM
Subject: Slow stepping


Hi,

I would like to know if others see/feel that the debugging is quite 
slow now. I have an AMD64 3200+, 1GB DDR RAM, gdb 6.6, and when I 
execute a debugger command, it can take 3-4 seconds until the debugger 
buttons are enabled. As I see the delay comes when the 

(gdb) -var-update *

command is executed.

Is it possible to speed this up? It makes stepping over quite annoying. 
If the retrieving of variables really takes so much time, I'd suggest 
one or both of the following:
- don't retireve it, if the variables widget is hidden (and do it as 
soon as it is shown)
- delay the retrieval, and do it only if there was no debugging activity 
for 1-2 seconds. 

Andras
-- 
Quanta Plus developer - http://quanta.kdewebdev.org
K Desktop Environment - http://www.kde.org
_______________________________________________
KDevelop-devel mailing list
KDevelop-devel at kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel