Bug 57716 - when main() is exitted, program should be executed until terminate
Summary: when main() is exitted, program should be executed until terminate
Status: RESOLVED INTENTIONAL
Alias: None
Product: kdevelop
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Mandrake RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: KDevelop Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-04-25 21:15 UTC by jozef.behran
Modified: 2003-05-10 04:18 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description jozef.behran 2003-04-25 21:15:01 UTC 
Version:            (using KDE KDE 3.1)
Installed from:    Mandrake RPMs
OS:          Linux

Imagine the situation: I'm debugging a program. Stepping through the code I will reach the end of main(). When I issue "Step Over" now (or similar command) the program will stop somewhere out of the scope of my source codes and the call stack will say I'm at "0x400387F7 in __libc_start_main() from /lib/somewhere/i/dont/know/where/libc.so.6" or something similar. I must issue the command again to get out of the program completely.

Expected behavior is to let the program run until it is terminated without the spurious break in the situation described above.
Comment 1 Jens Dagerbo 2003-05-10 04:18:03 UTC 
I disagree. I can certainly imagine this information being useful to someone and 
handle main() as a special case just adds complexity to the code for no (IMHO) 
benefit. 
 
If you are at the end of main() simply press "continue" instead of "step out" if you 
want the program to run to the end.