http://bugs.winehq.org/show_bug.cgi?id=16162
--- Comment #8 from Colin Pitrat colin.pitrat@gmail.com 2009-02-17 14:53:51 ---
From winedbg, the call to wine_server_call could be done from the following
stack: Wine-dbg>bt Backtrace: =>0 0xb80b2422 (0x7ec0364c) 1 0x7efc1fa5 NTDLL_wait_for_multiple_objects+0x275() in ntdll (0x7ec0386c) 2 0x7efc22a8 NtWaitForMultipleObjects+0x68() in ntdll (0x7ec0389c) 3 0x7ee5aff2 WaitForMultipleObjectsEx+0x102() in kernel32 (0x7ec039dc) 4 0x7ee5b1ec WaitForSingleObject+0x3c() in kernel32 (0x7ec039fc) 5 0x007b2bcf in s3 (+0x3b2bcf) (0x7ec03a38) 6 0x7efc5322 call_thread_func+0x42() in ntdll (0x7ec03ad8) 7 0x7efc550e start_thread+0x14e() in ntdll (0x7ec043c8) 8 0xb7f24155 start_thread+0xc5() in libpthread.so.0 (0x7ec044b8) 9 0xb7ea7a5e __clone+0x5e() in libc.so.6 (0x00000000)
However, I'm not familiar enough with winedbg to check content of the request object.