[Bug 57710] New: automatic breakpoint at program beginning

[jbb]

Hi,

It works in the way I want it to work (which is not to say that it's correct 
:-). ATM I don't consider this a bug but a wishlist.

I don't understand what advantage you see in making the user explicitly start 
the program after loading the executable. Could you explain your reasoning.

Also note that in kdevelop3 breakpoints are re-loaded on a project reload so 
you only ever have to set the br once not each time you load the project.

Actually I do see one advantage but your suggestion of a br at main doesn't 
solve it. For anyone that really wants to examine the program startup (ie the 
code _before_ main) they cannot do it with kdevelop yet. But that's a very 
unusual thing to want to do, and you'll probable be better of using gdb from 
the command line.

jbb

On Sat, 26 Apr 2003 03:23, jozef.behran at krs.sk wrote:
> ------- You are receiving this mail because: -------
> You are the assignee for the bug, or are watching the assignee.
>
> http://bugs.kde.org/show_bug.cgi?id=57710
>            Summary: automatic breakpoint at program beginning
>            Product: kdevelop
>            Version: unspecified
>           Platform: Mandrake RPMs
>         OS/Version: Linux
>             Status: UNCONFIRMED
>           Severity: normal
>           Priority: NOR
>          Component: general
>         AssignedTo: kdevelop-devel at kdevelop.org
>         ReportedBy: jozef.behran at krs.sk
>
>
> 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?
>
> _______________________________________________
> Kdevelop-devel mailing list
> Kdevelop-devel at barney.cs.uni-potsdam.de
> http://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel