Bug#648764: More informative backtrace

[Michel Dänzer]

On Die, 2011-11-15 at 00:51 +0100, Cyril Brulebois wrote: 
> 
> Jan Oberländer <mindriot at gmx.net> (14/11/2011):
> > I suppose it's a good thing this bug reproduces so well. :)  Here's a
> > better backtrace.
> 
> thanks for that. But you could also install libdrm's debug packages I
> think. ;-)
> 
> (Getting a core and exploiting it afterwards is usually a nice idea: you
> can install more packages as needed, without having to get a new crash.
> Hints at http://x.debian.net/howto/use-gdb.html)
> 
> > -- gdb output:
> > #3  0xb729db28 in *__GI___assert_fail (assertion=0xb6f98287 "boi->space_accounted", file=0xb6f9826a "../../radeon/radeon_cs_gem.c", line=181, function=0xb6f982ba "cs_gem_write_reloc") at assert.c:81
> >         buf = 0xb8fff898 "Xorg: ../../radeon/radeon_cs_gem.c:181: cs_gem_write_reloc: Assertion `boi->space_accounted' failed.\n"
> > #4  0xb6f96384 in ?? () from /usr/lib/i386-linux-gnu/libdrm_radeon.so.1
> > No symbol table info available.
> > #5  0xb6f971a2 in radeon_cs_write_reloc () from /usr/lib/i386-linux-gnu/libdrm_radeon.so.1
> > No symbol table info available.
> 
> ^^^^
> for those

That shouldn't be necessary. As in the other bug, the libdrm_radeon
assertion failure is probably just a symptom of the bug in the radeon
driver.


-- 
Earthling Michel Dänzer           |                   http://www.amd.com
Libre software enthusiast         |          Debian, X and DRI developer