https://bugs.documentfoundation.org/show_bug.cgi?id=158129
--- Comment #21 from V Stuart Foote <[email protected]> --- With windbg opened and the soffice.bin attached and running, issue a windbg console command to load the symbols ".reload /f" (it will take a while to download). Then continue to run soffice.bin by issuing the "g" command. On crash/lockup you'd issue a "~* kp" command in the windbg console (any missing symbols will be added) and then the thread stack will dump to the windbg console. The first thread segment of the listing will hold the faulting issue. Look it over and see if anything jumps out. You can run an "!analyze -v" to from windbg console for automated "feedback" on the event. If not obvious what the fault is, save the windbg console content for both commands to a text file and then attach. The stack trace for the threads and the analyze output will include the symbol details (identify the line of the calling source, if the symbols are available, the Intel and nVidia symbols for their drivers won't be) and we'd know more precisely the issue. -- You are receiving this mail because: You are the assignee for the bug.
