On Fri, 05 Dec 2003 11:12:55 +0000, you wrote:
Certainly a backtrace of the deadlock would be interesting, if it is the Xi bug it'll look like this:
#0 0x0f04e044 in sigsuspend () from /lib/libc.so.6 #1 0x0f17cadc in __pthread_wait_for_restart_signal () from /lib/libpthread.so.0 #2 0x0f17ec3c in __pthread_alt_lock () from /lib/libpthread.so.0 #3 0x0f17b02c in pthread_mutex_lock () from /lib/libpthread.so.0 #4 0x0ef7e700 in _XLockDisplay (dpy=0x10056640) at locking.c:478 #5 0x0edf2238 in XGetExtensionVersion (dpy=0x10056640, name=0xedf5a18 "XInputExtension") at XGetVers.c:108 #6 0x0edf4dfc in _XiCheckExtInit (dpy=0x10056640, version_index=1) at XExtInt.c:198 #7 0x0edf3004 in XListInputDevices (dpy=0x10056640, ndevices=0x7ffff67c) at XListDev.c:85
| (gdb) bt | #0 0x4010e8ab in read () from /lib/libc.so.6 | #1 0x4020a448 in __JCR_LIST__ () from /usr/local/lib/wine/ntdll.dll.so | #2 0xffffffe0 in ?? () | #3 0x401ee2b2 in wait_reply (cookie=0x406cf6c4) at ../../include/winnt.h:1524 | #4 0x401ee5d2 in NTDLL_wait_for_multiple_objects (count=1, handles=0x406cf794, flags=12, timeout=0x406cf7c0) | at sync.c:585 | #5 0x401ee676 in NtWaitForMultipleObjects (count=12, handles=0x406cf7c0, wait_all=2066163, alertable=0 '\0', | timeout=0x401f870e) at sync.c:603 | #6 0x406cf794 in ?? () | #7 0x0000000c in ?? () | #8 0x406cf7c0 in ?? () | #9 0x001f86f3 in pe_load.0 () | Cannot access memory at address 0x118000
Not the same thing, even not a lot of X in it. What I did was starting the program; wait for the deadlock messages; start gdb; attach the pid of the single wine thread; get the back trace. I hope that is correct.
More suggestions what I can try are welcome.
Rein.