https://bugs.documentfoundation.org/show_bug.cgi?id=117099
V Stuart Foote <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEEDINFO
CC| |[email protected]
Ever confirmed|0 |1
--- Comment #1 from V Stuart Foote <[email protected]> ---
The crash recover should result in a crashreport (a dump posted to
crashreport.libreoffice.org that is parsed with symbols) we'll need that.
If not generated, check the task manager for any soffice.bin instances left
running, kill them and retest. Post the linked crash report.
Otherwise if you are up to it, you could install the Windows SDK, just the
debug tools, and catch the crash dump with linked symbols [1]; and, might need
to use the Microsoft sysinternals "procdump" utility [2] to catch the dump with
-ma settings to create the dump.
Devs won't be able to do a lot with this crash at the 6.0.3.2 x64 build without
seeing a dump/stack trace linked to Libreoffice symbols.
=-ref-=
[1] https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg
[2] https://docs.microsoft.com/en-us/sysinternals/downloads/procdump
--
You are receiving this mail because:
You are the assignee for the bug._______________________________________________
Libreoffice-bugs mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
