On 12/02/2016 01:26 AM, Markus Mohrhard wrote:
Hey,
seems that the Og change has quite some negative consequences for the
debugging experience..
Normally in dbgutil builds all the variables were available and none of
them would be optimized away. I just started debugging and already had a
number of gdb messages telling me that the variable has been optimized
away. I never experienced the same problem before in a dbgutil build.
Does anyone else see this problem?
i noticed it too, gdb sometimes displays "<optimized out>" when the
variable is not yet or no longer live, and mentioned it in the ESC
meeting, but nobody sounded bothered by that.
i haven't seen a live variable that gdb wouldn't display.
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.