Roland Scheidegger wrote:
Adam K Kirchhoff wrote:
Thanks for the tip. I updated to not only the latest Mesa cvs and
drm cvs, but the latest xorg cvs. This is a vast improvement, and
XFCE4
works with DRI enabled. But... glxgears segfaults:
(gdb) run
Starting program: /usr/X11R6/bin/glxgears
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 5369)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 5369)]
0x00000000 in ?? ()
(gdb) bt
#0 0x00000000 in ?? ()
#1 0xb7a300e4 in execute_list (ctx=0x805e7b8, list=145) at
main/dlist.c:6420
#2 0xb7a30940 in _mesa_CallList (list=1) at main/dlist.c:6749
#3 0xb7a81a3d in neutral_CallList (i=1) at vtxfmt_tmp.h:304
#4 0xb7e8d615 in glCallList (list=1) at glapitemp.h:85
Try this patch here:
http://marc.theaimsgroup.com/?l=mesa3d-dev&m=112337787415898&w=2
That should fix the issue. I believe it not only fixes it, but it's
the right thing to do, mesa maps the gl vertex attrib functions (such
as glNormal) to glVertexAttribNV functions somewhere in the display
list code - and the dispatch offsets for these won't exist otherwise
(unless you have a driver which claims to support NV_vertex_program).
Someone might want to check this in (with a better comment...), I
can't until next week.
Roland
Roland,
Thanks! That fixed the crahes for me.
Adam
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
