Bug#648764: More informative backtrace

2011-12-05 Thread Michel Dänzer
On Sam, 2011-11-26 at 22:43 +0100, Jan Oberländer wrote: > On Thu, Nov 17, 2011 at 11:24:24AM +0100, Michel Dänzer wrote: > > Can you try if the patch below fixes this crash? > > Heh. I wish I could tell you. Before testing the patch I tried to > reproduce the crash, just to make sure I could a

Bug#648764: More informative backtrace

2011-11-26 Thread Jan Oberländer
On Thu, Nov 17, 2011 at 11:24:24AM +0100, Michel Dänzer wrote: > Can you try if the patch below fixes this crash? Heh. I wish I could tell you. Before testing the patch I tried to reproduce the crash, just to make sure I could actually tell it was gone afterwards. Turns out I can't reproduce it

Bug#648764: More informative backtrace

2011-11-24 Thread Jan Oberländer
Hi, On Thu, Nov 17, 2011 at 11:24:24AM +0100, Michel Dänzer wrote: > Can you try if the patch below fixes this crash? Sorry for the late reply, I've been out of town. I'll see if I can try your patch this weekend. Best, Jan -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with

Bug#648764: More informative backtrace

2011-11-17 Thread Michel Dänzer
On Mon, 2011-11-14 at 22:23 +0100, Jan Oberländer wrote: > > #6 0xb705ae55 in R200TextureSetupCP (pPict=0xb904a8a0, pPix=, > unit=0) at ../../src/radeon_exa_render.c:878 > #7 0xb706629f in R200PrepareCompositeCP (op=3, pSrcPicture=0xb904a8a0, > pMaskPicture=0x0, pDstPicture=0xb9002020, pSrc=0x

Bug#648764: More informative backtrace

2011-11-15 Thread Michel Dänzer
On Die, 2011-11-15 at 00:51 +0100, Cyril Brulebois wrote: > > Jan Oberländer (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

Bug#648764: More informative backtrace

2011-11-14 Thread Cyril Brulebois
Hi, Jan Oberländer (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

Bug#648764: More informative backtrace

2011-11-14 Thread Jan Oberländer
Hello again, I suppose it's a good thing this bug reproduces so well. :) Here's a better backtrace. -- gdb output: Program received signal SIGABRT, Aborted. 0xb75d3424 in __kernel_vsyscall () (gdb) bt full #0 0xb75d3424 in __kernel_vsyscall () No symbol table info available. #1 0xb72a4911 in *