Summary: | [r300g] SIGSEGV src/mesa/vbo/vbo_exec_array.c:1154 | ||
---|---|---|---|
Product: | Mesa | Reporter: | Vinson Lee <vlee> |
Component: | Mesa core | Assignee: | mesa-dev |
Status: | CLOSED FIXED | QA Contact: | |
Severity: | critical | ||
Priority: | medium | ||
Version: | git | ||
Hardware: | x86 (IA32) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: | define IN_DRI_DRIVER |
Description
Vinson Lee
2010-11-11 18:16:23 UTC
I can't reproduce this, but it looks like a Mesa core bug. I can't reproduce this with any other driver. The piglit test in question doesn't call glMultiDrawElements() at all so I don't see how we'd wind up in that function unless something in API dispatch was broken. Nobody else has reported anything like that. Can you try a clean rebuild of Mesa, Vinson? mesa: a172368ef1500fd2c7c1e55133e8e098b73d97a5 (master) I retested with a clean build and it still crashing with the identical backtrace. What is your setup? It seems your libGL.so and the DRI driver use different versions of glapi, and IN_DRI_DRIVER is not defined when building the DRI driver. Created attachment 40430 [details] [review] define IN_DRI_DRIVER Does this patch help? The attachment (id=40430) fixes the SIGSEGV. The patch should also fix bug 31569. This should be a candidate for the 7.9 branch. commit bb045d339b53f7ddd42bfca363e3d589b0ddcf20 Author: Chia-I Wu <olv@lunarg.com> Date: Sat Nov 20 17:47:11 2010 -0800 scons: Define IN_DRI_DRIVER. The define is required for DRI drivers. It is not needed for libgl-xlib, but the overhead it introduces should be minor. diff --git a/src/mesa/SConscript b/src/mesa/SConscript index 5fe5d39..08d731d 100644 --- a/src/mesa/SConscript +++ b/src/mesa/SConscript @@ -19,6 +19,10 @@ if env['platform'] == 'windows': 'WIN32_THREADS', # use Win32 thread API ]) env.Prepend(CPPPATH = ['#src/talloc']) +else: + env.Append(CPPDEFINES = [ + 'IN_DRI_DRIVER', # enable the remap table (for DRI drivers) + ]) # # Source files |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.