On Fri, Sep 7, 2012 at 7:24 PM, Michael Meeks <michael.meeks@suse.com> wrote:
Hi John,
You can always make it easier for a developer to solve - and the easier
it is, the more likely it is to get solved quickly. Ways to do that are:
* getting a stack-trace with full debugging symbols
* running valgrind with full debugging symbols and
attaching a trace.
If this is the case, maybe pre-build binaries with full debugging
symbols should be made available for download (more) easily: both for
releases and daily master builds ? Also, a 'howto' on how to do this
(on linux, with gdb, on windows, with windbg ?) would be nice to have
?
- John Smith.
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.