[Xcb] print backtraces in case an assert fails inside xlib/xcb

Barton C Massey bart at cs.pdx.edu
Thu Jun 7 18:10:00 PDT 2007


In message <20070607172401.40708794 at comet> you wrote:
> FWIW, here's the Gentoo bug related to XCB issues (Look at the "depends
> on" area for the bugs it's related to):
> 
> http://bugs.gentoo.org/show_bug.cgi?id=3D174434
> 
> The two main issues are 1) Java and 2) libtool .la contamination causing
> the switch between XCB and no-XCB to be a lot more painful than it
> should be.

Thanks much for the pointer!

The Java bug really is a problem; we're trying to figure out
what to do about it in Debian now too.  Sun's licensing
tries to make it impossible for us to ship fixed bits or
even to auto-fix them post-shipment, as near as we can tell.
(I'm not sure that last is even legal, but who wants to go
there?)

As far as I can tell at this point, though, no concrete bug
reports for other apps since that ball of X libs was fixed a
bit ago?

I don't understand the ".la contamination" issue.  Could
someone who understands it please enlighten me?

Again, thanks much.

    Bart


More information about the Xcb mailing list