Created attachment 37448 [details]
compiz crash backtrace
I bisected and got this:
ba2cc3b8e6ad161181b67fd2575c6bc768584d23 is the first bad commit
Author: Brian Paul <email@example.com>
Date: Thu Jul 29 13:49:21 2010 -0600
gallium: implement bounds checking for constant buffers
Plumb the constant buffer sizes down into the tgsi interpreter where
we can do bounds checking. Optional debug code warns upon out-of-bounds
reading. Plus add a few other assertions in the TGSI interpreter.
:040000 040000 7141c078038120e29bab2e275fb935f20731c0ff e2f4d072421db8d000922127dc1f707145b73c61 M src
The thing is the Draw module in Gallium has 3 codepaths:
- Slow interpreter
- SSE code generation (broken)
Guess what, yeah, you use the broken one.
The SSE codepath will most probably be dropped, so I am closing this bug as WONTFIX.
Now you have two options to fix your setup:
1) Compile Mesa with --enable-gallium-llvm to get the LLVM codepath.
2) Set the environment variable GALLIUM_NOSSE=1 to use the slow interpreter.
Fixed by commit aef4500ca4ae9e5bc57560c6f9a32d9ad892975b.
(In reply to comment #2)
> Fixed by commit aef4500ca4ae9e5bc57560c6f9a32d9ad892975b.
With latest mesa master the same symptoms persist here.
(In reply to comment #3)
> (In reply to comment #2)
> > Fixed by commit aef4500ca4ae9e5bc57560c6f9a32d9ad892975b.
> With latest mesa master the same symptoms persist here.
DISREGARD this comment. It is indeed fixed (bug report # mixup)