https://bugs.documentfoundation.org/show_bug.cgi?id=98125
--- Comment #15 from [email protected] --- 1. I think you should have mentioned that WinDng will ask to save something to the workspace after attaching to it. Does accepting the suggestion OK? 2. Although you mentioned that WinDbg might be used when LibreOffice hang, you didn't supply full instructions for that case. Here is what happened: I was about to open a document by browsing the file system. I clicked open, navigated to the directory the file to be opened was in, and then started WinDbg. I saw only a single soffice.bin process. Attached it to WinDbg, and clicked to open the file. The last few lines I got in the WinDbg window so far were: (b60.b10): Break instruction exception - code 80000003 (first chance) eax=7ffd9000 ebx=00000001 ecx=00000002 edx=00000003 esi=00000004 edi=00000005 eip=7c90120e esp=0724ffcc ebp=0724fff4 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 0:012> g (b60.fd8): C++ EH exception - code e06d7363 (first chance) (b60.fd8): C++ EH exception - code e06d7363 (first chance) (b60.fd8): C++ EH exception - code e06d7363 (first chance) (b60.fd8): C++ EH exception - code e06d7363 (first chance) Nothing was changed for about 15 minutes. WinDbg stated *BUSY* Debugger is running. I couldn't see in your instructions what should I do, so I selected Debug -> Break. If I got it correctly, WinDbg only the following new lines added, (b60.4d0): Break instruction exception - code 80000003 (first chance) eax=7ffd9000 ebx=00000001 ecx=00000002 edx=00000003 esi=00000004 edi=00000005 eip=7c90120e esp=0724ffcc ebp=0724fff4 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 Now LibreOffice Window was hidden by WinDbg and the browser windows, and I couldn't switch to it. So I again let it Debug -> Go. Other then a single 0:010> g line, I saw nothing new in WinDbg window. At that point I decided to kill LibreOffice. In the task manager there was a single, Not Responding, LibreOffice application. In the Processes list of the task manager, I saw one soffice.bin. I choose to END Process it. Was I to choose End Process Tree? As a consequence, WinDbg got the following lines added: eax=00000000 ebx=0000006b ecx=7ffd7000 edx=19d99c48 esi=01de8218 edi=00000144 eip=7c90e514 esp=16e1fd08 ebp=16e1fd40 iopl=0 nv up ei pl zr na pe nc cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000246 ntdll!KiFastSystemCallRet: 7c90e514 c3 ret And the LibreOffice application was gone. Doesn't seem sensible to analyze, but what do I know? 0:011> !analyze -v Last event: b60.fd8: Exit process 0:b60, code 1 debugger time: Tue Mar 8 15:51:26.662 2016 (UTC + 0:00) -- 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
