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

[Christoph Pfister]

[ re-adding xcb list to CC ]

Am Donnerstag, 7. Juni 2007 19:02 schrieb a r:
> On 6/7/07, Christoph Pfister <christophpfister at gmail.com> wrote:
> > lxuser at pdln:/tmp$ ./main
> > Got a backtrace:
> > #0 /tmp/usr/lib/libxcb-xlib.so.0 [0xb7f9d728]
> > #1 /tmp/usr/lib/libxcb-xlib.so.0(xcb_xlib_unlock+0x31) [0xb7f9d861]
> > #2 ./test.so(function_a+0x11) [0xb7f9f3fd]
> > #3 ./test.so(function_b+0x11) [0xb7f9f410]
> > #4 ./main [0x80484a7]
> > #5 /lib/libc.so.6(__libc_start_main+0xdc) [0xb7e60ebc]
> > #6 ./main [0x80483f1]
> > main: xcb_xlib.c:82: xcb_xlib_unlock: Assertion `c->xlib.lock' failed.
> > Aborted
>
>   ^^^^^^^
>
> Is there any chance that this assert will be removed?

No; okay - as I don't decide that I should say "most likely not" ...

> If not, what is the policy regarding support for patched XCB?

I don't understand your question here - what kind of policy?

> BTW, what is the reason behind this assert? Will disabling it result
> in crash of xserver or system?

No, but the assert is because of a clear bug somewhere which has to be fixed 
and not just ignored.

> \R.

Christoph