Bug#613593: xserver-xorg-video-radeon: [regression] X fails to start
On Mon, 2011-02-21 at 22:03 +0100, Stephen Kitt wrote:
> Investigating further, it turns out that X actually starts if it's
> started on its own (rather than via gnome-session). Starting xterm
> etc. works OK, it's after gnome-session starts that everything blows
> up. I started X under gdb and got the following backtrace when it
> segfaulted after gnome-session started:
Which window/compositing manager does your GNOME (3?) session use? If it
uses OpenGL, this might be one of the GLX/DRI2 drawable life cycle
issues about which there are a few reports upstream.
> Program received signal SIGSEGV, Segmentation fault.
> 0xb7d4390c in _int_free (av=<value optimized out>, p=0x861c730) at malloc.c:4957
> 4957 malloc.c: No such file or directory.
> in malloc.c
> (gdb) bt
> #0 0xb7d4390c in _int_free (av=<value optimized out>, p=0x861c730) at malloc.c:4957
> #1 0xb7d46bbd in __libc_free (mem=0x861c738) at malloc.c:3739
> #2 0x0808cc24 in RegionDestroy (pReg=0x861c738) at ../../dix/region.c:256
> #3 0xb7a45f58 in exaHWCopyNtoN (pSrcDrawable=0x861b040, pDstDrawable=0x861cd20, pGC=0x0, pbox=0xbfffd74c, nbox=1, dx=-16, dy=0,
> reverse=0, upsidedown=0) at ../../exa/exa_accel.c:555
I fail to see what can go wrong with that region in exaHWCopyNtoN(), so
presumably this is an after-effect of a problem that occurred earlier,
e.g. memory corruption. If you can get the X server running in valgrind,
that might give a hint.
Earthling Michel Dänzer | http://www.vmware.com
Libre software enthusiast | Debian, X and DRI developer