Bug#33312: adding a "run to end of {} block" debugging command

digitale at digitaleric.net digitale at digitaleric.net
Thu Oct 4 20:10:34 UTC 2001


Package: kdevelop
Version: 2.0.1 (using KDE 2.2.1 )
Severity: wishlist
Installed from:    compiled sources
Compiler:          gcc version 2.95.3 20010315 (release)
OS:                SunOS (sun4u) release 5.8
OS/Compiler notes: 

I've just discovered KDevelop, and I really love it.  One feature that I think would be very useful would be to add a debugging command that would run until the program reaches the end of the current block {}(enclosed by curly braces).  It would be similar to "run until end of function/stack frame", but more fine-grained.

The Watcom debugger had this, and I have not found another debugger that can do this since I've had to switch.  It is great if you are stepping through a function which has many loops, because you can just run the whole loop without having to manually set and then clear a breakpoint.

I don't know how difficult it would be to implement this, but I think the following method would work:
	-find the "}" which closes this group
	-set a breakpoint for the line after it
	-tell the debugger to "run to end of function/stack-frame" (this will catch a return() in case it happens inside the loop).
	-clear the breakpoint once the program is paused by the debugger

I'd be willing to implement this myself, but I'm pretty new to KDevelop/gdb, so if anyone could give me some advice on where to start, I'd appriciate it.

Thanks!
-Eric Northup

(Submitted via bugs.kde.org)
(Called from KBugReport dialog)


-
to unsubscribe from this list send an email to kdevelop-devel-request at kdevelop.org with the following body:
unsubscribe »your-email-address«



More information about the KDevelop-devel mailing list