Re: [AD] Allegro on multi-processor machines

[ Thread Index | Date Index | More lists.liballeg.org/allegro-developers Archives ]


Evert Glebbeek wrote:
The test program comes up normally, but it freezes after a time. This can be
short or fast, and isn't related to any action by me. A backtrace by gdb seems
to point to _xwin_unlock, suggesting that it is a race condition of some kind.

Is this with or without using X to draw the cursor? If it's Allegro drawing the cursor, it's probably Xlib hitting an async as it tries to draw the mouse in the timer thread and something else elsewhere.

I honestly can't think of a way to fix this since if you force a call to XLOCK and don't increment the lock count, the next graphic routine will halt as it tries to lock again, though if you *do* increment the lock count, the main program's drwing routines will happilly try to do their thing.

I am also unable to set a fullscreen X11 mode, although the XVidMode extension
is available. This leaves the system in a screwed up resolution and I can't get
keyboard control in X until I start another Allegro program. I don't think this
is related though.

Not totally. That happens when Allegro has the keyboard driver installed and gets the mode switched, but Allegro then bombs out and doesn't properly close it's X display handle. Or something along those lines.

- Kitty Cat




Mail converted by MHonArc 2.6.19+ http://listengine.tuxfamily.org/