Bug 33312 - adding a "run to end of {} block" debugging command
Summary: adding a "run to end of {} block" debugging command
Status: RESOLVED INTENTIONAL
Alias: None
Product: kdevelop
Classification: Applications
Component: kdevelop 2.x (obsolete) (show other bugs)
Version: 2.0.1
Platform: Compiled Sources Solaris
: NOR wishlist
Target Milestone: ---
Assignee: KDevelop-Devel List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-10-04 20:18 UTC by digitale
Modified: 2002-09-16 14:43 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description digitale 2001-10-04 20:10:34 UTC
(*** This bug was imported into bugs.kde.org ***)

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)
Comment 1 John Firebaugh 2002-09-15 21:44:28 UTC
The "Run to Cursor" command suffices and is more flexible to boot.