http://bugs.winehq.org/show_bug.cgi?id=31882
--- Comment #43 from Erich Hoover ehoover@mines.edu 2012-10-24 12:04:06 CDT --- (In reply to comment #42)
There's still something broken in libxcb 1.9. Here's the backtrace of a deadlock from running arial32.exe:
#0 0xf77e1425 in __kernel_vsyscall () #1 0xf7643f02 in __lll_lock_wait () from /lib/i386-linux-gnu/i686/cmov/libpthread.so.0 #2 0xf7641a77 in pthread_cond_signal@@GLIBC_2.3.2 () from /lib/i386-linux-gnu/i686/cmov/libpthread.so.0 #3 0x7e741fb5 in _xcb_in_wake_up_next_reader (c=0x7da05060) at xcb_in.c:623 #4 0x7e740a00 in _xcb_out_send (c=0x7da05060, vector=0x0, count=0) at xcb_out.c:352 #5 0x7e7407c9 in xcb_writev (c=0x7da05060, vector=0x53e5b8, count=3, requests=6) at xcb_out.c:297 #6 0x7e798440 in _XSend () from /usr/lib32/libX11.so.6 #7 0x7e79886a in _XFlush () from /usr/lib32/libX11.so.6 #8 0x7e778ef1 in XFlush () from /usr/lib32/libX11.so.6 #9 0x7e8eca8b in create_x11_physdev (drawable=346) at init.c:116
Thanks so much, that's exactly what I need to try and look into this. So far I've been unable to reproduce the arial32 problem :/