<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Opening a file LO says it previously crashed, but fails to recover (win10 only?)" href="https://bugs.documentfoundation.org/show_bug.cgi?id=127845#c44">Comment # 44</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Opening a file LO says it previously crashed, but fails to recover (win10 only?)" href="https://bugs.documentfoundation.org/show_bug.cgi?id=127845">bug 127845</a> from <a class="email" href="mailto:tim@tim-passingham.co.uk" title="tim@tim-passingham.co.uk">tim@tim-passingham.co.uk</a> <pre>(In reply to vesper from <a href="show_bug.cgi?id=127845#c40">comment #40</a>) > In reference to your query "Can you install a debug/development version of > libreoffice and get the resulting crash report to the people at Libreoffice? > That might help them to help us." on > windows10forums.com/threads/multiple-applications-have-broken-after-9-26- > windows-update.20437/#post-102525, I got so far as downloading the WinDbg > tool referenced in Julien's post (<a href="show_bug.cgi?id=127845#c34">comment 34</a>) (and that wiped out my Windows > update history), installing it and trying to run it. I discovered then that > I couldn't attach to the LO process, no doubt because I don't (yet) have the > LO debug version installed. I'll get back to that, but not until sometime > next week at the earliest... The windows update history is just a log file, and sometimes misleading (particularly if you do a rollback to a restore point). I use the admin version of cmd systeminfo.exe to see what is actually installed.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>