Uwe Bonnes <bon(a)elektron.ikp.physik.tu-darmstadt.de> writes:
"Ferenc" == Ferenc Wagner <wferi(a)afavant.elte.hu> writes:
... Ferenc> kernel32.WaitForSingleObject(0000003c,ffffffff) ret=40593e4c [5
Somewhere before an CreateEvent Call with a return value of 0000003c must happen. Look at that event and why it doesn't trigger.
You are right, there is. I create the event before forking off the dialog thread, which calls CreateDialog then SetEvent, which I didn't show you in the source snippets, only the Wait which you quoted. But I think it was not this Wait which timed out, but the tsx11_lock in CreateDialog. For me it seems XCreateDC does not return (the one I quoted from the Wine source). I mean, sometimes. Because the same program works now... I did not even recompile it, honest. I am going mad. Yesterday night it was 100% reproducible. Instead of this: 000a:Ret gdi32.GetObjectType() retval=00000003 ret=409ee125 000a:Call ntdll.RtlEnterCriticalSection(40a20700) ret=409fe8b0 000a:Ret ntdll.RtlEnterCriticalSection() retval=00000000 ret=409fe8b0 trace:x11drv:X11DRV_CreateDC physDev=[I lost the number] err:ntdll:RtlpWaitForCriticalSection section 0x40334040 "?" wait timed out in thread 000a, blocked by 0009, retrying (60 sec) now I get 000a:Ret gdi32.GetObjectType() retval=00000003 ret=409ee125 000a:Call ntdll.RtlEnterCriticalSection(40a20700) ret=409fe910 000a:Ret ntdll.RtlEnterCriticalSection() retval=00000000 ret=409fe910 trace:x11drv:X11DRV_CreateDC physDev=0x40347ab8 trace:x11drv:X11DRV_CreateDC XCreateGC returned 0x101322a8 000a:Call ntdll.RtlLeaveCriticalSection(40a20700) ret=409fe934 000a:Ret ntdll.RtlLeaveCriticalSection() retval=00000000 ret=409fe934 000a:Ret x11drv.CreateDC() retval=00000001 ret=40899405 I've got the impression, that my network connection (remote X) is slower now, but not sure... Will see if it break again. Feri.