https://bugs.documentfoundation.org/show_bug.cgi?id=91770
--- Comment #33 from Yousuf (Jay) Philips <[email protected]> --- Created attachment 123396 --> https://bugs.documentfoundation.org/attachment.cgi?id=123396&action=edit another backtrace (In reply to V Stuart Foote from comment #32) > With WinDbg running and attached to an soffice.bin process... > Open the File -> Symbol File Path dialog. > > The Path should show the local CACHE, and the SRV for Kendy's TB39, possibly > Cloph's production symstor, and the SRV for Microsoft VS. Basically the > string from the How to get a backtrace Wiki. > > At the bottom of the dialog is a "Reload" check box--check that and OK. Same > can also be done issuing a ".reload" command. Would be good to add the reload info to the wiki. > What I do is take the LibreOffice session near to where I expect the error > to occur, then Debug -> Break, and issue the "~* kp" to force the symbol > lookup. > It takes some time, but then most of the symbols are resolved and held in > cache--you can tell in resulting the stack trace(s) if the symbol lookup are > populating. Couple rounds of that. > > Then "g" to continue the run and allow the crash--this time with a pretty > full symbol cache to work against. You'll get a good stack trace, and the > "!Analyze -v" may be more complete. Gave it another shot, so hope its sufficient. -- 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
