I also added some display commands to show you the details of the critical
section in question. Now, if you look at what the display says you'll
notice something odd: at first crit = 0x0011d1e0, but then it switches to
0x403112b8. And this is without any breakpoints having been set up within
RtlEnt
"Sami Aario" <[EMAIL PROTECTED]> writes:
> See how after four calls to RtlEnterCriticalSection, LockCount starts to be
> 0? So a pretty good theory is that the critical section is acquired, and
> then not released, during the loading and initialization of
> /usr/X11R6/lib/libXrender.so.1.
Most li
Hi all,
I decided to investigate this old bug:
http://www.winehq.com/hypermail/wine-devel/2003/12/0158.html
even though Alexander removed thread initialization from x11drv. So the
first thing I did was apply this patch:
Index: x11drv_main.c
==
