https://bugs.documentfoundation.org/show_bug.cgi?id=99006
--- Comment #20 from R. Bingham <[email protected]> ---
Win dump file captured using Task Manager on a running but unresponsive
instance of LO Writer with a scratch new text doc and first command in Writer
is Insert->TOC. Task Manager shows LO Writer consistent at ~17% CPU on a
4-core Intel i7. Security context is an *un*privileged user.
Attached text file is a listing of the WinDbg !analyze -v command run against
the dump file as a privileged user. Some items:
+ I used the symbol path list from the Wiki page copy/paste. Note WinDbg
complains it could not find a symbol file but alas does not indicate which one.
Someone please test the symbol data path given on the Wiki page as possibly
stale.
+ I note in the listing FAULTING_SOURCE_LINE indicates use of Cygwin64
components in LO. I am running Cygwin64 daemons syslog-ng and cygserver on
this machine, managed using the Windows/Computer Management/Service
infrastructure. Is there any indication in the LO end-user doc of dependence
on Cygwin or does the LO install or app startup test for an existing instance
of Cygwin and version compatibility if the is important?
I really, really, really suggest someone provide some detailed guidance for
parameter choices for MS ProcDump if that will increase the value that can be
extracted from a dump analysis.
Note: The WinDbg command 'kp' merely lists a summary stack trace of a stopped
process. One actually has to understand breakpoint debugging to know you have
to stop the process in the first place. I have that listing as well but it is
not that informative.
--
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
