https://bugs.documentfoundation.org/show_bug.cgi?id=142022
--- Comment #12 from V Stuart Foote <vstuart.fo...@utsa.edu> ---
(In reply to Nico from comment #11)
> Not checked by default...
> Checked, and same crash.
>
> Gave a try, after deleting my LO profile, I checked it (along with Skia
> which came back)... and also failing :/
OK those were all the simple steps, next would be to obtain a back trace. It
will work better against the 7.1 builds compared to against master/7.2 because
the symbols are fully published for the release builds, but it is involved to
get set up. Steps are here:
https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg
It is a hassle but it would really help to isolate the component causing the
crashes on your system. Unfortunately the generic !analyze -v (or !analyze -f)
command will often not resolve, and you have to use a "~* kp" to list the stack
with symbols for all the threads to tease out the call(s) causing the crash.
A local WinDbg run can do a more complete stack trace than what is submitted by
the automated mini-dump based crash reporting mechanism, which you have already
reported against the generic mergedlo.dll.
The whole WinDbg tool can be a challenge.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
