On 25 Jan, Damjan Jovanovic wrote:
> Hi
>
> For a while I've noticed how gbuild modules don't have debug symbols unless
> built with the maximum debug level ("./configure --enable-debug" globally
> or "build debug=true" per module) which also produces oceans of log
> messages we usually don't want.
>
> In r1780246, I've finally changed debugging in gbuild to match how dmake
> works: --enable-symbols and --enable-crashdump now also add debug symbols
> to gbuild modules like they do to dmake modules, and the
> --enable-symbols=small option is also implemented for GCC and Clang (sorry
> Windows developers, MSVC doesn't seem to have it). The only extra benefit
> of --enable-debug on top of this now, is that it disables compiler
> optimizations - should we disable them for --enable-symbols too?
I would say no. Consider the case where there is a crash when the code
is compiled with optimization, but not when the code is compiled without
optimization. Having the symbols for the former case is still useful
for finding the location of the crash even if a lot of the variables
that you might want to look at are optmiized out.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
