[Xcb] Re: [Xlibs] Quick XCL, implemented

Jim Gettys Jim.Gettys@hp.com
Mon, 03 Nov 2003 09:19:56 -0500


Jamey,

Also note that Xt/Motif brings in other dependencies, on the
Xlib locale implementation, Xmu, and the like, that GTK apps don't
care about (currrent Qt still has these dependencies, though due
to some mail I sent Mattias a few weeks ago, future Qt stuff should
no longer be linked against Xt, Xmu, etc...; it doesn't actually
use anything though, so you might not notice.). Xt/Motif actually uses
this crud, however.

An easy way to check this out is to run a convenient Motif app;
about the only one I personally run regularly any more is
Acrobat reader (acroread).  Note that the X locale stuff isn't
working this instant on fd.o Xlibs; we have to autofoo it yet.


Sequence lost messages usually means some corruption of the protocol
buffers, which can either be threading or other disasters...
                             - Jim

On Mon, 2003-11-03 at 09:58, Christopher Blizzard wrote:
> Jamey Sharp wrote:
> 
> >Mozilla is the only completely broken exception I've seen. Keith had
> >suggested it might be using a custom threads library, which wouldn't
> >work alongside XCB since XCB uses pthreads only. Everything else looks
> >like it's running correctly, though I fairly frequently get "Xlib:
> >sequence lost" messages. I'm hoping somebody will help me fix that.
> >
> Mozilla uses pthreads.  It also runs the entire UI on a single thread so 
> we're not going to be writing to the X queue from more than one thread 
> at a time.  I'm betting you're not seeing something thread-related.
> 
> There are some interesting things that Mozilla does do, though.  We do 
> hunt around in the queue from time to time looking for certain events 
> and removing them.  Also when we load plugins that use Xt we actually 
> open a second connection to the X server for the Xt mainloop to use.  So 
> it's possible that might be causing part of the problem.  Other than 
> that we're a pretty standard X app.
> 
> --Chris
-- 
Jim Gettys <Jim.Gettys@hp.com>
HP Labs, Cambridge Research Laboratory