RE: [AD] race condition in X11

["Vincent Penecherc'h" <Vincent.Penecherch@xxxxxxxxxx>]

> I think it should be checked at a `deeper' level, but I'm not 
> sure I have a 
> clear picture of the problem.

Possibly, I don't have a clear picture either :)
I think it's a pretty dangerous thing to have here anyway, two
such routines are likely to be called nested, and only one
nesting is OK from what I understand from src/gui.c.

> Anyway, you should let X draw the cursor for you and not 
> bother with Allegro's 
> soft cursor :P

Don't forget I was away for more than a year, there were no
os cursors in my day ;)

> > It doesn't track the number of 
> > calls, though, so it will screw up the nesting.
> 
> This is a bug though.

It actually does a weird thing: there's an automatic unlock
after a "complex" operation. That has to be intended...
The release op (it's not unacquire, sorry, just looked up the
name) doesn't do anything, so even if it doesn't keep track
of nesting, it seems proofed against nesting mismatch, though
I don't see the interest of doing this, since I thought the
point of it was to tell Allegro when you were doing batch ops
so it could setup the hardware to be faster. But then that's
just what I recall from a few years ago, and I could be wrong
(again).




______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________