Christophe Strobbe <email@example.com> wrote:
Someone who actually needs LibreOffice and who has the time should install
debug symbols and get stack traces.
Is there any guidance anywhere on how to do this?
Under the Debian distribution (and possibly others) there is a libreoffice-dbg
package that contains the debug symbols. the first step would be to install
The second step would be to run LibreOffice under gdb to obtain back traces
when there is a segmentation fault.
Alternatively, you could enable the creation of core files:
ulimit -c unlimited
which will create a core file whenever a program crashes. You can then use gdb
to examine the core file.
I am sure there are instructions specific to LibreOffice available somewhere.
Someone who knows the internals of LibreOffice well and who is skilled in
debugging C++ code should be able to find and fix the bugs.
Unsubscribe instructions: E-mail to firstname.lastname@example.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/accessibility/
All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-accessibility] Should Writer export taggedPDF and bookmarks by default? · Tom Davies
- Re: [libreoffice-accessibility] Should Writer export taggedPDF and bookmarks by default? (continued)
Impressum (Legal Info)
: 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