How to find out locking problem

[Henri Verbeet]

On 2 January 2011 13:59,  <wylda at volny.cz> wrote:
> err:ntdll:RtlpWaitForCriticalSection section 0x7de77580
> "x11drv_main.c: X11DRV_CritSection" wait timed out in thread 001c,
> blocked by 0041, retrying (60 sec)
>
...
> Backtracing for thread 001c in process 001b (C:\Program Files\2K
> Games\BioShock\Builds\Release\Bioshock.exe):
> Backtrace:
>
> =>0 0xb77dc422 __kernel_vsyscall+0xe() in [vdso].so (0x0073f918)
>
> 1 0x7bc7fbbe NTDLL_wait_for_multiple_objects+0x1f0(count=0x73fafc,
> handles=0x73f9fc, flags=0x4, timeout=0x7bc8c082,
> signal_object=0x73fa58)
> [/build/wine-git_build/dlls/ntdll/sync.c:1124] in ntdll (0x0073fb28)
>
> 2 0x7bc7fbbe NTDLL_wait_for_multiple_objects+0x1f0(count=0x1,
> handles=0x73fbb0, flags=0x4, timeout=(nil), signal_object=0x0(nil))
> [/build/wine-git_build/dlls/ntdll/sync.c:1124] in ntdll (0x0073fb78)
>
> 3 0x7bc7fcae NtWaitForMultipleObjects+0x73(count=0x1,
> handles=0x73fbb0, wait_all=0, alertable=0, timeout=(nil))
> [/build/wine-git_build/dlls/ntdll/sync.c:1162] in ntdll (0x0073fcc8)
>
> 4 0x7b86e395 WaitForMultipleObjectsEx+0x138(count=0x1,
> handles=0x73fd00, wait_all=0, timeout=0xffffffff, alertable=0)
> [/build/wine-git_build/dlls/kernel32/sync.c:188] in kernel32
> (0x0073fcf8)
>
> 5 0x7b86e1c9 WaitForSingleObject+0x3b(handle=0x7f4,
> timeout=0xffffffff) [/build/wine-git_build/dlls/kernel32/sync.c:128]
> in kernel32 (0x0073fd10)
>
>From that backtrace, it doesn't look like 001c is waiting for a
critical section at all.