https://bugs.freedesktop.org/show_bug.cgi?id=50421
--- Comment #35 from Christian Schroeder <cbkschroe...@yahoo.ca> --- OK, I've done the best I can. I've uploaded the file "backtrace 14120900.txt". I need to provide some context, though. I've got the pre-crash state snapshotted in my VM, so I can test again and again with reasonable speed. I can reproduce the %PERCENT% error state (and the subsequent crash with the required additional pressing of "Download") again and again up until I attach to the soffice.bin process. That is, I can have WinDbg running but unattached, and reliably produce both the %PERCENT% and the crash. If I attach to the process immediately after starting LO, however, then WinDbg seems to hang for quite a few moments on line 148: "(8b4.ae4): Break instruction exception - code 80000003 (first chance)". Only after a few moments does WinDbg advance to the remainder: eax=7ffdf000 ebx=00000001 ecx=00000002 edx=00000003 esi=00000004 edi=00000005 eip=7c90120e esp=0dadffcc ebp=0dadfff4 iopl=0 nv up ei pl zr na pe nc cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000246 ntdll!DbgBreakPoint: 7c90120e cc int 3 After it's gone to this point and I start debugging, LO will NOT produce the %PERCENT% error and, consequently, I cannot reproduce the crash. More detail: Route 1: 1) I start WinDbg; 2) I start LO; 3) In LO, I attempt to check for updates; %PERCENT% appears and I can cause the crash. Route 2: 1) I start WinDbg; 2) I start LO; 3) I attach to soffice.bin; 4) I wait as I mentioned above; 5) After I see "int 3", I hit F5; 6) I check for updates; 7) LO does nothing remarkable; everything seems to work fine. In order to obtain my backtrace file, then, I did the following: 1) I start WinDbg; 2) I start LO; 3) In LO, I attempt to check for updates; %PERCENT% appears; 4) I attach WinDbg to soffice.bin; I wait; 5) After I see "int 3", I hit F5; 6) I press "Download", the crash occurs, and I proceed with the exception analysis. Please let me know if you have any further questions. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
