> * Some thread id ?? grabs the X11 lock
> * Thread 0x3c attempts to delete a device context, so deadlocks on the
> X11 lock while inside a syslevel
> * Thread 0x2f writes to a DIB, triggering a fault which is handled by
> Wine and then we also try to enter the syslevel held by 0x3c, so we
> deadlo
On Wed, 15 Oct 2003, Mike Hearn wrote:
> I might as well point out (as I didn't find this intuitive when I was
> learning) that you do that like this:
>
> 1) Open up a new terminal window
> 2) Run winedbg
> 3) "walk process"
> 4) Locate the win32 process id of the program that has deadlocked
> 5) "
> > err:ntdll:RtlpWaitForCriticalSection section 0x40969e80
> > "../../objects/gdiobj.c: GDI_level" wait timed out in thread 0009, blocked
> > by 0015, retrying (60 sec)
> > err:ntdll:RtlpWaitForCriticalSection section 0x40f227a0 "x11drv_main.c:
> > X11DRV_CritSection" wait timed out in thread 0015
I got this from running Panzer General 3 (which you can get for free at
http://www.the-underdogs.org):
err:ntdll:RtlpWaitForCriticalSection section 0x40969e80
"../../objects/gdiobj.c: GDI_level" wait timed out in thread 0009, blocked
by 0015, retrying (60 sec)
err:ntdll:RtlpWaitForCriticalSection
