On 17/11/10 18:50, Santiago Bosio wrote:
Hi!
When LibO is built using --enable-symbols, it still uses -O2
optimizations, making hard to debug execution with GDB.
So, I think that it should default to -O2 on a normal build, and to
-O0 when using --enable-symbols. Don't see the point of using
optimizations when building a version for debugging purposes.
What if it's the optimisation that introduces the bug? Completely
different product (MS VB :-) but I know of a very nasty bug that only
crops up in compiled mode - you prove the code is correct in interpreted
mode, compile it, and the executable fails ...
Cheers,
Wol
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.