On 30 November 2010 11:34, Joe Smith <jes@martnet.com> wrote:
I was also having a lot of trouble learning anything from running OOo under
gdb. Gdb was acting weird and I couldn't step through the code and poke
around. I ended up trying to do it by adding a printf, rebuild, run, rinse,
repeat. No fun; less progress.
Did you turn off compiler optimisations? I had the same problem (gdb
hopping around in a non-intuitive way, and the values of some useful
variables were optimised out) until I turned them off.
If that's the problem, you can do it by configuring with
--enable-debug, or if you're just building a single module you can do
"build -- debug=t dbglevel=2"
I think "dbglevel=1" also turns them off, and will give less noise,
but I haven't checked.
Cheers,
Mattias
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.