Bug#648764: More informative backtrace

Michel Dänzer daenzer at debian.org
Mon Dec 5 08:46:23 PST 2011

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 actually tell it was gone
> afterwards.  Turns out I can't reproduce it anymore, because WordPress
> (where I originally encountered the crash, reliably) seem to have
> changed something in their web interface, and I can't reproduce the
> crash anymore.  I haven't installed any upgrades since I reported the
> bug, so my system's behavior should still be the same.  Murphy's Law, I
> guess. :)
> Testing out your patch at least didn't make anything worse.  But I'm
> going back to the original version right now to wait and see if I can
> discover some other way to reproduce the crash.
> Maybe you have an idea of how I could reproduce it, based on the gdb
> trace I sent?

Not really, unfortunately.

If you encounter a similar problem in the future, you could try creating
a trace of the triggering operations, e.g. with cairo-trace.

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

More information about the xorg-driver-ati mailing list