Ouch, that was 189 MB for nothing then :) Well, it can still prove useful. >From looking closer at the backtrace, we can see that the stack is clearly messed up, since it has addresses like 0x00000001 and 0xffffffff. If this crash is reproducible, it should be possible to define a breakpoint (for instance on r200UpdateTextureState?) and enable it just before making it crash. From there on, see how far you can get with stepping or refining breakpoints until you get a backtrace while it still uncorrupted. I admit this can be quite an exercise in gdb... A good introduction is on http://www-128.ibm.com/developerworks/library/l-gdb/
** Bug watch added: freedesktop.org Bugzilla #12164 https://bugs.freedesktop.org/show_bug.cgi?id=12164 ** Also affects: mesa via https://bugs.freedesktop.org/show_bug.cgi?id=12164 Importance: Unknown Status: Unknown -- [r200] radeon dri and blender in gutsy https://bugs.launchpad.net/bugs/174479 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
