Hi Markus,
On 28/03/2019 16:13, Markus Mohrhard wrote:
so in general the fastest way to get some feedback might be to ping me
directly and give me some time to look into such issues. While I still
have quite bad internet and can't do any uploads of symbol information I
can still at least quickly inspect the problem.
That would be wonderful ! =)
One general problem that we have is that we have no recent windows debug
symbol information. I tried to move that service from my local machine
to the server during the Munich hackfest but did not manage to replicate
my setup well enough that valid symbol information are generated. Sadly
this has some knock-on effects as can be seen by some of the unresolved
crash reports. At least on Windows getting a backtrace requires that
enough of the stack pointers can be guessed from the dumped stack. This
relies to some to degree on the system symbol informations.
Interesting.
As soon as I have a non-mobile internet connection again I'll either run
a full set of system symbol download on my machine or finish the work on
moving that service to the server.
Much appreciated ! our top crasher is (obviously) the one without any
symbol information that lurks in libmerged currently ;-)
Regards,
Michael.
--
michael.meeks@collabora.com <><, GM Collabora Productivity
Hangout: mejmeeks@gmail.com, Skype: mmeeks
(M) +44 7795 666 147 - timezone usually UK / Europe
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.