[Xcb] Re: xcblock.c Assertion

Thu Sep 14 17:53:58 PDT 2006

It looks like this problem is still in the current git files.

I did a git checkout master; ./autogen.sh ; make ; make install
(this was at about 8:30 PM EDT on 9/14)

Then started up X and my apps started crashing again.  Here is the gdb log:
-----------
$ gdb gaim
GNU gdb 6.1.1
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i486-slackware-linux"...Using host
libthread_db library "/lib/libthread_db.so.1".

(gdb) run
Starting program: /usr/local/bin/gaim
Detaching after fork from child process 18563.
gaim: xcl/xcblock.c:128: _XGetXCBBuffer: Assertion `((int) ((xcb_req)
- (dpy->request)) >= 0)' failed.

Program received signal SIGABRT, Aborted.
0x406b51b1 in kill () from /lib/libc.so.6
(gdb) bt
#0  0x406b51b1 in kill () from /lib/libc.so.6
#1  0x404a09c1 in pthread_kill () from /lib/libpthread.so.0
#2  0x404a0ccb in raise () from /lib/libpthread.so.0
#3  0x406b4df4 in raise () from /lib/libc.so.6
#4  0x406b65a8 in abort () from /lib/libc.so.6
#5  0x406ae56c in __assert_fail () from /lib/libc.so.6
#6  0x407b4ee0 in _IO_2_1_stdout_ () from /lib/libc.so.6
#7  0xbfcbd591 in ?? ()
#8  0x407adfe6 in in6addr_loopback () from /lib/libc.so.6
#9  0x40638771 in xrmtypes () from /usr/X11R7/lib/libX11.so.6
#10 0x00000080 in ?? ()
#11 0x406387aa in xrmtypes () from /usr/X11R7/lib/libX11.so.6
#12 0x407adfe6 in in6addr_loopback () from /lib/libc.so.6
#13 0x406388e0 in xrmtypes () from /usr/X11R7/lib/libX11.so.6
#14 0x4000a490 in _dl_map_object_deps () from /lib/ld-linux.so.2
Previous frame inner to this frame (corrupt stack?)
--------------

Does that help any?

Paul

On 9/13/06, Barton C Massey <bart at cs.pdx.edu> wrote:
> All of this is quite useful, thanks.  In particular, it's
> good to know it's an x86 Linux box with a current vanilla
> kernel (we always worry about the lack of testing on weird
> platforms) and that it's current XCB bits.
>
> Anything you can do at this point to reproduce the problem
> would be hugely helpful; in any case, thanks again!
>
>         Bart
>
> In message <c19f80250609130605o1e27454bx7ee40ae49cb3ca1d at mail.gmail.com> you wrote:
> > Sure, I can try.  What is important to tell you?
> >
> > $ uname -a
> > Linux aramaki 2.6.17.11 #13 Tue Sep 12 20:14:39 EDT 2006 i686 unknown
> > unknown GNU/Linux
> >
> > $ lspci
> > .....
> > 00:1f.3 SMBus: Intel Corp. 82801EB/ER (ICH5/ICH5R) SMBus Controller (rev 02)
> > 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R350
> > [Radeon 9800]
> > .....
> >
> > I was using a git pull which was done on 2006-09-03.
> >
> > Anything else?
> >
> > I don't have the old xorg.conf from when the error was occurring, so I
> > can't give that to you but I'm pretty sure it was just the vanilla
> > result of X --configure.  After work today if I have time, I'll take a
> > shot at recreating the problem with the current git and see if that
> > fixes anything.  If I'm able to get it working (breaking) again, I'll
> > run gdb on an app and see what happens and send you the backtrace and
> > my current xorg.conf.
> >
> > Oh, at the time, I was running with the vesa driver.  Since then, I
> > have been able to get fglrx to work, so I should be able to do a test
> > with both.
> >
> > Last bit I remember - It only happened when the mouse was over the
> > window.  If I started up, say, gaim and it popped up somewhere off to
> > the side, everything would work just fine.  Then, as soon as I moved
> > the mouse over the window, it crashed with that same error.
> >
> > I'll try to get some more info later on for you.
> >
> > Paul
> >
> > On 9/13/06, Barton C Massey <bart at cs.pdx.edu> wrote:
> > > Paul, thanks hugely for reporting this, and Jeremy, thanks
> > > hugely for forwarding it.
> > >
> > > Paul, can you give some details about platform and about the
> > > version of XCB you had installed?  This might help us to
> > > diagnose the problem.  I'm wondering if old XCB bits with
> > > various bugs were responsible---we've seen things like that
> > > before.
> > >
> > >         Bart Massey
> > >         bart at cs.pdx.edu
> > >
> > > In message <Pine.LNX.4.44.0609111147340.376-100000 at groucho.unet.brandeis.edu> you wrote:
> > > > Paul, it looked like an XCB error.  I forwarded your message to the xcb
> > > > list.  Someone will look into it.
> > > >
> > > > Jeremy
> > > >
> > > > On Mon, 11 Sep 2006, Paul Moss wrote:
> > > >
> > > > > I just upgraded to Xorg -current and I had a problem running
> > > > > some programs.  Firefox, most notably, also gaim, xchat (I think all
> > > > > gtk apps) crash on load with this error:
> > > > >
> > > > > xcl/xcblock.c:128: _XGetXCBBuffer: Assertion `((int) ((xcb_req) -
> > > > > (dpy->request)) >=0)' failed.
> > > > >
> > > > > I am not sure how to get more information for that particular error.
> > > > > It has happened in both fluxbox and enlightenment.  And I have seen it
> > > > > with more than 1 program, so I assume that it is related to my recent
> > > > > upgrade of X.
> > > > >
> > > > > I rolled back from the master branch in the git repos for the
> > > > > lib/libX11 package to the 'stable' branch and recompiled.  Everything
> > > > > appears to be working fine now.  Anyway, I just thought you all might
> > > > > want to know.  Apologies if it was just something stupid I was doing.
> > > > >
> > > > > Paul
> > > > > _______________________________________________
> > > > > xorg mailing list
> > > > > xorg at lists.freedesktop.org
> > > > > http://lists.freedesktop.org/mailman/listinfo/xorg
> > > > >
> > > >
> > > > _______________________________________________
> > > > Xcb mailing list
> > > > Xcb at lists.freedesktop.org
> > > > http://lists.freedesktop.org/mailman/listinfo/xcb
> > >
>