On 29/04/2012 13:00, Hans-Peter Diettrich wrote:
Martin schrieb:
On 29/04/2012 09:56, Jürgen Hestermann wrote:
Also, I guess it is more error prone. Compile with external debug,
then make changes, recompile but with release settings. Then you have
an outdated debug info file, and if you happen to run that in the
debugger, you get a lot of strange things....
Give the executable different names. When debugging, the exe name is
irrelevant since the application will be started by F9.
Then you can always generate 2 exe too. One with and one without dbg info...
If you generate, the 2 exe individually, people may debug their latest
changes, and then ship the release exe, from the day before....
I am not saying, that external debug info could not be made default. And
neither do I say, that the current solution has no problems (it
obviously has)
In fact I think it would be great if it could be changed to use external
dbg info (assuming it is done right).
Just pointing out, it is probably not as easy, as just a new default for
that checkbox.
- Test it on various platforms, cross compile, remote debug, ....
(ideally add to the debugger test suit)
- Test it for projects with starter/host application (debug libraries
with external info)
- different gdb versions (at least 7.0 to 7.4 / 6.3.50 on Mac)
- implement checks in the IDE so no old file will be used accidental
(different name; or remove/rename old dbg info file)
Maybe other things I haven't thought of.
In any case, while nice to have, it is nothing I am going to bother
about. There is plenty other, that I find more important.
--
_______________________________________________
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
