does there exists a written step-by-step tutorial, how to debug LO using
Visual Studio, which is suitable for beginners?
1) Build with --enable-dbgutil --enable-debug on Windows.
2) Run the application in question from instdir/program.
3) Run VS and from Debug menu, click Attach to Process...
4) Find soffice.bin from the list (the title will help you find the correct
application, in case you have many running).
5) Set a breakpoint, break, continue, and enjoy debugging.
Notice that this will not load the LO project or anything fancy like that.
This is just purely for debugging. But it works perfectly well if you build
LO correctly.
If you open the correct source in VS (after attaching to soffice.bin) and
place a breakpoint, VS will know that it's part of the LO binary you are
debugging.
You can also save this solution so you can reopen the same files with
breakpoints at a later time to redo a similar debugging session.
On Thu, Jul 30, 2015 at 5:24 PM, Regina Henschel <rb.henschel@t-online.de>
wrote:
Hi all,
does there exists a written step-by-step tutorial, how to debug LO using
Visual Studio, which is suitable for beginners? Or can someone guide me? I
have never used Visual Studio up to now.
I want to look why the MathML import has become so bad in LO (tdf#75171).
Kind regards
Regina
_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice
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.