https://bugs.documentfoundation.org/show_bug.cgi?id=100362
--- Comment #7 from V Stuart Foote <[email protected]> ---
Since there is no "crash" there is nothing that an "!analyse -v" to reveal.
Rather, bring the LibreOffice session close to where you'd like it, and then
attach the soffice.bin process to the WinDbg utility. Check the symbol source
is pointing to the LibreOffice symbol servers as in the Wiki.
run a "lml" command, and then a "~*kp" stack trace for all threads-- this loads
symbols, updating any that are not yet cached locally.
Issue a "g" command to be sure LibreOffice is running, then open your IBM
iSeries Client Access (pscws.exe), if it hangs LibreOffice in the WinDbg
console take a "~*kp" stack trace and allow any additional symbols to load.
Or, if need break into LibreOffice (from Debug -> Break menu) and then run the
stack trace with "~*kp"
See if anything interesting shows in any of the threads. Of course you can
also attach to the pscws.exe or one of its processes as well--but not sure
where you'd find useful symbols to the program and would only have MicroSoft's.
--
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
