Bug 57710

Summary:	automatic breakpoint at program beginning
Product:	[Applications] kdevelop	Reporter:	jozef.behran
Component:	general	Assignee:	KDevelop Developers <kdevelop-devel>
Status:	RESOLVED DUPLICATE
Severity:	wishlist
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Mandrake RPMs
OS:	Linux
Latest Commit:		Version Fixed In:

Description jozef.behran 2003-04-25 17:23:55 UTC

Version:           2.1.5 (using KDE KDE 3.1)
Installed from:    Mandrake RPMs
Compiler:          gcc 3.2.2 See Mandrake 9.1 distribution for the compiler
OS:          Linux

When I create a program and issue the "Debug" command, the program is started, but it is impossible to debug it. It is only possible to "run it at full speed". To be able to step through the code I must put a breakpoint somewhere and run the program until it hits the breakpoint.

How about an automatic breapoint placed on the beginning of the main() function everytime the debugger is started and running the program until it hits it? Or something similar?

Comment 1 Amilcar do Carmo Lucas 2003-05-12 14:09:02 UTC

This is not general enough (some programing languages don't even have a main)! 
The 41166 whish is simular, but more realistic. 
Marking this as a duplicate of that whish  

*** This bug has been marked as a duplicate of 41166 ***

Comment 2 jozef.behran 2003-05-13 11:59:08 UTC

> This is not general enough (some programing languages don't even have a main)!

When I was using DJGPP, I found a command called "Main function" (I cannot
determine, where, because I don't have DJGPP handy right now, I only guess that
it is under the "Run" pulldown submenu). This command allowed me to enter a name
of a function and then when the debugger was invoked, it ran the program to the
beginning of the function specified by this command and then stopped (like if I
placed the cursor on the beginning of the function, invoked "Go to cursor" and
then returned the cursor where it was before). The default function for this
command was main() (DJGPP is mainly used by C/C++ programmers). I think this can
be very useful in KDevelop too. And I think that this feature is common for all
languages that have functions.

The bug 41166 is about automatically invoking the debugger when user issues the
"Goto cursor" command and I don't think it is a duplicate of this.

Now I found a more general idea how to accomplish my wish, so the RESOLVED
DUPLICATE state is good. See bug 58419 for the more general idea.