Christophe Strobbe <accessibility@global.libreoffice.org> 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 it. 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 accessibility+help@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ 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