Bugzilla – Attachment 123560 Details for
Bug 98646
Hang when double-clicking item in navigator
Home
|
New
|
Browse
|
Search
|
[?]
|
Reports
|
Help
|
New Account
|
Log In
[x]
|
Forgot Password
Login:
[x]
Trace of hang
hang_trace.txt (text/plain), 12.28 KB, created by
Buovjaga
on 2016-03-14 14:10:30 UTC
(
hide
)
Description:
Trace of hang
Filename:
MIME Type:
Creator:
Buovjaga
Created:
2016-03-14 14:10:30 UTC
Size:
12.28 KB
patch
obsolete
>******************************************************************************* >* * >* Exception Analysis * >* * >******************************************************************************* > >************************************************************************* >*** *** >*** *** >*** Either you specified an unqualified symbol, or your debugger *** >*** doesn't have full symbol information. Unqualified symbol *** >*** resolution is turned off by default. Please either specify a *** >*** fully qualified symbol module!symbolname, or enable resolution *** >*** of unqualified symbols by typing ".symopt- 100". Note that *** >*** enabling unqualified symbol resolution with network symbol *** >*** server shares in the symbol path may cause the debugger to *** >*** appear to hang for long periods of time when an incorrect *** >*** symbol name is typed or the network symbol server is down. *** >*** *** >*** For some commands to work properly, your symbol path *** >*** must point to .pdb files that have full type information. *** >*** *** >*** Certain .pdb files (such as the public OS symbols) do not *** >*** contain the required information. Contact the group that *** >*** provided you with these symbols if you need this command to *** >*** work. *** >*** *** >*** Type referenced: ntdll!_PEB *** >*** *** >************************************************************************* >************************************************************************* >*** *** >*** *** >*** Either you specified an unqualified symbol, or your debugger *** >*** doesn't have full symbol information. Unqualified symbol *** >*** resolution is turned off by default. Please either specify a *** >*** fully qualified symbol module!symbolname, or enable resolution *** >*** of unqualified symbols by typing ".symopt- 100". Note that *** >*** enabling unqualified symbol resolution with network symbol *** >*** server shares in the symbol path may cause the debugger to *** >*** appear to hang for long periods of time when an incorrect *** >*** symbol name is typed or the network symbol server is down. *** >*** *** >*** For some commands to work properly, your symbol path *** >*** must point to .pdb files that have full type information. *** >*** *** >*** Certain .pdb files (such as the public OS symbols) do not *** >*** contain the required information. Contact the group that *** >*** provided you with these symbols if you need this command to *** >*** work. *** >*** *** >*** Type referenced: ntdll!_HEAP_FAILURE_INFORMATION *** >*** *** >************************************************************************* >************************************************************************* >*** *** >*** *** >*** Either you specified an unqualified symbol, or your debugger *** >*** doesn't have full symbol information. Unqualified symbol *** >*** resolution is turned off by default. Please either specify a *** >*** fully qualified symbol module!symbolname, or enable resolution *** >*** of unqualified symbols by typing ".symopt- 100". Note that *** >*** enabling unqualified symbol resolution with network symbol *** >*** server shares in the symbol path may cause the debugger to *** >*** appear to hang for long periods of time when an incorrect *** >*** symbol name is typed or the network symbol server is down. *** >*** *** >*** For some commands to work properly, your symbol path *** >*** must point to .pdb files that have full type information. *** >*** *** >*** Certain .pdb files (such as the public OS symbols) do not *** >*** contain the required information. Contact the group that *** >*** provided you with these symbols if you need this command to *** >*** work. *** >*** *** >*** Type referenced: nt!IMAGE_NT_HEADERS32 *** >*** *** >************************************************************************* > >FAULTING_IP: >ntdll!DbgBreakPoint+0 >7716000c cc int 3 > >EXCEPTION_RECORD: ffffffff -- (.exr 0xffffffffffffffff) >ExceptionAddress: 7716000c (ntdll!DbgBreakPoint) > ExceptionCode: 80000003 (Break instruction exception) > ExceptionFlags: 00000000 >NumberParameters: 1 > Parameter[0]: 00000000 > >CONTEXT: 00000000 -- (.cxr 0x0;r) >eax=7ef40000 ebx=00000000 ecx=00000000 edx=771efbaa esi=00000000 edi=00000000 >eip=7716000c esp=1d20f9f8 ebp=1d20fa24 iopl=0 nv up ei pl zr na pe nc >cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000244 >ntdll!DbgBreakPoint: >7716000c cc int 3 > >FAULTING_THREAD: 00000000 > >BUGCHECK_STR: HANG > >PROCESS_NAME: soffice.bin > >OVERLAPPED_MODULE: Address regions for 'dnd' and 'faultrep.dll' overlap > >ERROR_CODE: (NTSTATUS) 0xcfffffff - <Unable to get error code text> > >EXCEPTION_CODE: (NTSTATUS) 0xcfffffff - <Unable to get error code text> > >EXCEPTION_PARAMETER1: 00000000 > >APP: soffice.bin > >ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) x86fre > >DERIVED_WAIT_CHAIN: > >Dl Eid Cid WaitType >-- --- ------- -------------------------- > 7 2458.20d4 Speculated (Triage) --> > 0 2458.2494 Unknown > >WAIT_CHAIN_COMMAND: ~7s;k;;~0s;k;; > >BLOCKING_THREAD: 00002494 > >DEFAULT_BUCKET_ID: APPLICATION_HANG_BusyHang > >PRIMARY_PROBLEM_CLASS: APPLICATION_HANG_BusyHang > >LAST_CONTROL_TRANSFER: from 5536358c to 54f93a77 > >STACK_TEXT: >00beda44 5536358c 00000000 5b20bef0 00000000 sdlo!Point::X+0x7 >00bedae4 550ce368 0a33bae0 1868baa0 6a37b5d7 sdlo!sd::DrawViewShell::MakeVisible+0x25c >00bedba0 5536331e 00bedd38 17391f58 055051e0 sdlo!sd::DrawDocShell::GotoBookmark+0x618 >00bedbb4 5533f9a9 00bedd38 6a37b3d3 00000000 sdlo!sd::DrawViewShell::GotoBookmark+0x3e >00bedda4 55365e1f 00beded0 00beddc4 59d24962 sdlo!sd::DrawViewShell::ExecCtrl+0x1009 >00beddb0 59d24962 17391f58 00beded0 17391f58 sdlo!SfxStubDrawViewShellExecCtrl+0xf >00beddc4 59d24c0c 55365e10 00beded0 6f1d9e7e sfxlo!SfxShell::CallExec+0x12 >00bede48 59d29e54 17391f58 5561c548 00beded0 sfxlo!SfxDispatcher::Call_Impl+0x29c >00bede98 59d25bd5 17391f58 5561c548 00beded0 sfxlo!SfxDispatcher::_Execute+0x294 >00bedf04 59ff9ae1 188ae4e0 000015de 00000005 sfxlo!SfxDispatcher::Execute+0x125 >00bedf48 59c6a752 00bee47c 6f1da6c2 00000000 sfxlo!SfxViewShell::JumpToMark+0x71 >00bee6f4 59c6086f 12cf6c10 00bee714 59d24962 sfxlo!SfxApplication::OpenDocExec_Impl+0x2282 >00bee700 59d24962 054aa880 12cf6c10 054aa880 sfxlo!SfxStubSfxApplicationOpenDocExec_Impl+0xf >00bee714 59d3fa33 59c60860 12cf6c10 59c60860 sfxlo!SfxShell::CallExec+0x12 >00bee734 5508c75f 12cf6c10 055d48c0 6a378667 sfxlo!SfxShell::ExecuteSlot+0xc3 >00bee810 55087b7f 12cf6c10 00bee830 59d24962 sdlo!SdModule::Execute+0x47f >00bee81c 59d24962 05505160 12cf6c10 05505160 sdlo!SfxStubSdModuleExecute+0xf >00bee830 59d24c0c 55087b70 12cf6c10 6f1da882 sfxlo!SfxShell::CallExec+0x12 >00bee8b4 59d28b76 05505160 55618ef8 12cf6c10 sfxlo!SfxDispatcher::Call_Impl+0x29c >00bee918 59d27f4f 12cf6c10 00bee938 59f38a33 sfxlo!SfxDispatcher::PostMsgHandler+0x116 >00bee924 59f38a33 188ae4e0 12cf6c10 188d36d8 sfxlo!SfxDispatcher::LinkStubPostMsgHandler+0xf >00bee938 59f38a56 12cf6c10 188d36d0 00bee954 sfxlo!Link<SfxRequest *,void>::Call+0x23 >00bee948 59f38a7f 12cf6c10 00bee968 5adeb543 sfxlo!SfxHintPoster::DoEvent_Impl+0x16 >00bee954 5adeb543 188d36d0 12cf6c10 172983ec sfxlo!SfxHintPoster::LinkStubDoEvent_Impl+0xf >00bee968 5adf17d8 12cf6c10 00bee984 5ac6e0d0 vcllo!Link<void *,void>::Call+0x23 >00bee980 5adf1ff5 172983e8 6f1daa6f 5b20bef0 vcllo!ImplHandleUserEvent+0x28 >00beeacc 5b202cbf 054f8970 00000016 172983e8 vcllo!ImplWindowFrameProc+0x695 >00beeae8 5b2081ac 00000016 172983e8 054f8cf0 vcllo!SalFrame::CallCallback+0x2f >00beeafc 5b20b747 002404c8 172983e8 735b16c4 vcllo!ImplHandleUserEvent+0x2c >00beeba0 5b20bf51 002404c8 00000482 00000000 vcllo!SalFrameWndProc+0x777 >00beebf0 751362fa 002404c8 00000482 00000000 vcllo!SalFrameWndProcW+0x61 >00beec1c 75136d3a 5b20bef0 002404c8 00000482 USER32!InternalCallWinProc+0x23 >00beec94 751377c4 00000000 5b20bef0 002404c8 USER32!UserCallWinProcCheckWow+0x109 >00beecf4 7513788a 5b20bef0 00000000 00beed18 USER32!DispatchMessageWorker+0x3bc >00beed04 5b1b80a6 00beed24 00000000 00f63080 USER32!DispatchMessageW+0xf >00beed18 5b1b8195 00beed24 002404c8 00000482 vcllo!ImplSalDispatchMessage+0x36 >00beed50 5b1b7f5b 00000001 00000000 00f63080 vcllo!ImplSalYield+0x55 >00beed84 5b0f0f5a 00000001 00000000 00000000 vcllo!WinSalInstance::DoYield+0xfb >00beefd0 5b0f30ee 00000001 00000000 00000000 vcllo!ImplYield+0x27a >00beefe4 5b0ef1fd 6f1db08f 00beeff4 04010110 vcllo!Application::Yield+0xe >00bef02c 734c0929 00bef660 734c57b1 6f1db60a vcllo!Application::Execute+0x1ad >00bef034 734c57b1 6f1db60a 00000000 00ed5a2e sofficeapp!desktop::Desktop::DoExecute+0x9 >00bef660 5b0f95fc 6f1db633 00bef698 00000001 sofficeapp!desktop::Desktop::Main+0x1811 >00bef690 5b0f9a6f 00000000 00bef710 734fd674 vcllo!ImplSVMain+0xbc >00bef69c 734fd674 6f1db77a 7356674c 00000000 vcllo!SVMain+0x2f >00bef710 00fd100a 6fa34d7d 00bef728 00fd103a sofficeapp!soffice_main+0x74 >WARNING: Stack unwind information not available. Following frames may be wrong. >00bef71c 00fd103a 00f0e858 00bef740 00fd1078 soffice+0x100a >00bef728 00fd1078 00000002 00f0e858 00000002 soffice!main+0x1a >00bef740 00fd12ce 00fd0000 00000000 00ed5a2e soffice!main+0x58 >00bef78c 74b4336a 7efde000 00bef7d8 77189882 soffice!main+0x2ae >00bef798 77189882 7efde000 762aa2c5 00000000 kernel32!BaseThreadInitThunk+0xe >00bef7d8 77189855 00fd119f 7efde000 00000000 ntdll!__RtlUserThreadStart+0x70 >00bef7f0 00000000 00fd119f 7efde000 00000000 ntdll!_RtlUserThreadStart+0x1b > > >FOLLOWUP_IP: >sdlo!SfxStubDrawViewShellExecCtrl+f [c:\cygwin\home\tinderbox\master\workdir\sditarget\sd\sdi\sdslots.hxx @ 1443] >55365e1f 5d pop ebp > >FAULTING_SOURCE_LINE: c:\cygwin\home\tinderbox\master\workdir\sditarget\sd\sdi\sdslots.hxx > >FAULTING_SOURCE_FILE: c:\cygwin\home\tinderbox\master\workdir\sditarget\sd\sdi\sdslots.hxx > >FAULTING_SOURCE_LINE_NUMBER: 1443 > >SYMBOL_STACK_INDEX: 5 > >SYMBOL_NAME: sdlo!SfxStubDrawViewShellExecCtrl+f > >FOLLOWUP_NAME: MachineOwner > >MODULE_NAME: sdlo > >IMAGE_NAME: sdlo.dll > >DEBUG_FLR_IMAGE_TIMESTAMP: 56dc86a5 > >STACK_COMMAND: ~0s ; kb > >BUCKET_ID: HANG_sdlo!SfxStubDrawViewShellExecCtrl+f > >FAILURE_BUCKET_ID: APPLICATION_HANG_BusyHang_cfffffff_sdlo.dll!SfxStubDrawViewShellExecCtrl > >ANALYSIS_SOURCE: UM > >FAILURE_ID_HASH_STRING: um:application_hang_busyhang_cfffffff_sdlo.dll!sfxstubdrawviewshellexecctrl > >FAILURE_ID_HASH: {fab3bb46-f98f-71e6-0768-d787d10c5d52} > >Followup: MachineOwner >--------- >
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 98646
: 123560