Problems with radeon_dri and Blender

Roland Scheidegger sroland at
Wed Jul 2 12:39:00 PDT 2008

On 02.07.2008 19:25, meino.cramer at wrote:
> Alex Deucher <alexdeucher at> [08-07-02 18:56]:
>> On Wed, Jul 2, 2008 at 12:17 PM,  <meino.cramer at> wrote:
>>> Hi,
>>> When using Blender my radeon_dri driver crashes with a segfault (and
>>> Blender follows :-/  ). But it only happens when some very specific actions
>>> are performed and only if the Shading ("Z") is activated for the 3D view.
>>> Currently I am only able to watch this. And dont know how to pinpoint
>>> the problem and whether the radeon_dri driver or Blender (or both) or
>>> the hardware habe a problem.
>>> If someone is interested, I will post an *.blend file to trigger the
>>> segfault.
>> The best starting point would be if you could get a backtrace from
>> blender using gdb.
> Here ist comes:
> solfire:/home/mccramer>gdb blender
> GNU gdb 6.7.1
> Copyright (C) 2007 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "i686-pc-linux-gnu"...
> Using host libthread_db library "/lib/".
> (gdb) run
> Starting program: /usr/local/bin/blender
> [Thread debugging using libthread_db enabled]
> [New Thread 0xb74af910 (LWP 24683)]
> Compiled with Python version 2.4.4.
> Checking for installed Python... got it!
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0xb74af910 (LWP 24683)]
> 0xb733f3e3 in vbo_split_prims () from /usr/lib/dri/
> (gdb) backtrace
> #0  0xb733f3e3 in vbo_split_prims () from /usr/lib/dri/
> (gdb)
> it is not that much, but....

Looks similar to
though this should be fixed in mesa 7.0.3. In any case a backtrace from
a debug build of the radeon dri driver would be more helpful...


More information about the xorg-driver-ati mailing list