Bug 58419

Summary:	Breakpoints placed to functions rather than source lines
Product:	[Applications] kdevelop	Reporter:	jozef.behran
Component:	CPP Debugger	Assignee:	KDevelop Developers <kdevelop-devel>
Status:	RESOLVED FIXED
Severity:	wishlist
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Mandrake RPMs
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description jozef.behran 2003-05-13 11:56:40 UTC

Version:           2.1.5 (using KDE 3.1.0)
Installed from:    Mandrake Linux Cooker i586 - Cooker
Compiler:          gcc version 3.2.2 (Mandrake Linux 9.1 3.2.2-3mdk)
OS:          Linux (i686) release 2.4.21-0.13mdk

I want to be able to define breakpoints "being at the beginning of function such and such". When I place the breakpoint on the function's beginning by hand, it is defined as "being at line such and such". KDevelop tries to track editing so the breakpoint will not go away when lines are added or removed but if I move the function definition somewhere, the breakpoint locations are lost.

Breakpoints "being at the beginning of function such and such" should during debugger initialization determine at which line the function starts and put breakpoints there. When I edit the source in a way that does not allow normal line breakpoints to survive (for example cutting the function definition from one file and pasting it into another file in the project), these breakpoints can survive, because it is always known, where the function they refers to is placed. 

When the function these breakpoints refers to does not exists, they should be made "pending" (as breakpoints placed into source code compiled without debugging support).

Comment 1 John Birch 2003-05-14 01:04:54 UTC

Strange - I'm already working on this :-) 
 
In the meantime when using gideon from cvs try the GDB window and enter "br functionname". It 
won't help in stopping at main but any other function will work. 
 
Don't raise a bug report about the GDB window - I've already have some fixes here - let the dust 
settle for a bit - mail me if you want though :-) 
 
jbb

Comment 2 John Birch 2003-05-14 19:00:22 UTC

Fixed in CVS