[Xcb] Nested XLockDisplay

[Elias Naur]

Hi Jeremy,

I'm not sure what version he is using, apparently the Debian testing
libraries as described in http://lwn.net/Articles/211808/. However, my
question was: does the assertion mean that you can't nest
XLockDisplay? If so, why has this changed from the old xlib which
seems to document that nesting is allowed?

 - elias

On 1/2/07, Jeremy A. Kolb <jkolb at brandeis.edu> wrote:
> Hi Elias,
>
> What version of the X11 server and libraries is the user using?  As far as
> I know all of the known LockDisplay/UnlockDisplay issues have been
> resolved in the latest versions.
>
> Jeremy
>
> On Tue, 2 Jan 2007, Elias Naur wrote:
>
> > Hi,
> >
> > Sorry if this is trivial or have been addressed before, but my
> > searching failed to bring up anything conclusive. My problem is the
> > LockDisplay/UnlockDisplay assertion failures in the xlib-on-xcb
> > library. I've got a LWJGL (http://lwjgl.org) user that complains that
> > the "xcb_xlib.c:41: xcb_xlib_lock: Assertion `!c->xlib.lock' failed."
> > occurs with aany test program. This is a java based library, but I
> > haven't yet tried to find out if the Sun java implementation or the
> > LWJGL library is at fault. As far as I can tell, the assertion means
> > that XLockDisplay has been called while the lock was already held.
> > However, the xlib manual at
> > http://tronche.com/gui/x/xlib/display/XLockDisplay.html states that
> > "Nested calls to XLockDisplay() work correctly; the display will not
> > actually be unlocked until XUnlockDisplay() has been called the same
> > number of times as XLockDisplay()". Have I misunderstood something or
> > has the spec changed with xlib-on-xcb to disallow nested XLockDisplay
> > (I can understand the other common assertion failure that occurs when
> > XUnlockDisplay is called without holding the lock)?
> >
> >  - elias
> > _______________________________________________
> > Xcb mailing list
> > Xcb at lists.freedesktop.org
> > http://lists.freedesktop.org/mailman/listinfo/xcb
> >
>
>