[Bug 51083] Deadlock in llvm-mingw compiled app

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=51083

--- Comment #20 from Vladimir Koković <vladimir.kokovic at gmail.com> ---
Now I have another situation when I did kill all wine processes !
After the start "bt all", this process is now waiting and does not open my
process 0110 but is in the "bt all" log file last process is 0104.

In my "pomocni-cross-llvm-mingw" log file is now logged in, after starting "BT
ALL" next:
0118:err:ntdll:RtlpWaitForCriticalSection section 000000007BC61540
"../wine/dlls/ntdll/loader.c: loader_section" wait timed out in thread 0118,
blocked by 0114, retrying (60 sec)
00bc:err:wineusb:event_thread_proc Error handling events: System call
interrupted (perhaps due to signal)
00bc:err:wineusb:event_thread_proc Error handling events: System call
interrupted (perhaps due to signal)
00bc:err:wineusb:event_thread_proc Error handling events: System call
interrupted (perhaps due to signal)
018c:err:ntdll:RtlpWaitForCriticalSection section 000000007BC61540
"../wine/dlls/ntdll/loader.c: loader_section" wait timed out in thread 018c,
blocked by 0114, retrying (60 sec)

When I do Kill "llvm-mingw-Linux>pomocni-llvm-mingw.exe" in "bt all" log file,
you can see the following at the end:
Process of pid=0110 has terminated
Exception c0000005

This is most likely to mean that winedbg cannot do attach to 0110 due to the
interrupt that occurred by the USB component.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.