drm is opened successfully according to output. backtrace (below) captured by gdb. Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1208166736 (LWP 15468)] 0x00000000 in ?? () #0 0x00000000 in ?? () #1 0x0023d1e2 in neutral_VertexAttrib4fvARB (index=1, v=0x1300) at main/vtxfmt_tmp.h:459 #2 0x0804a483 in ?? () #3 0x00b094ff in __libc_start_main (main=0x8049fe9, argc=1, ubp_av=0xbfbf1454, init=0x804ab34, fini=0x804ab90, rtld_fini=0xae4c9d <_dl_fini>, stack_end=0xbfbf144c) at ../sysdeps/generic/libc-start.c:231 #4 0x08049091 in ?? () #1 0x0023d1e2 in neutral_VertexAttrib4fvARB (index=1, v=0x1300) at main/vtxfmt_tmp.h:459 459 CALL_VertexAttrib4fvARB(GET_DISPATCH(), ( index, v ));
more specific please. Is this with direct rendering (in which case component should be drivers/dri/mach64) or are you using for some or another reason an indirect rendering fallback (LIBGL_DEBUG=verbose glxinfo should answer that). Also, are you using mesa cvs or what?
Looked like that function was in the body of the library, sorry. Changing component. Mesa from CVS on client side, but it's been segfaulting since 6.3.x, only just recently tried it again and got a trace. Server side is xorg from cvs, built with Mesa source from 6.4 branch, as it doesn't build against "6.5"
Closing after 7 years of silence. I think it's safe to assume this is fixed in current mesa, as the backtrace shows no mach64 driver functions, and AFAICT there were no problems with vertex handling in mesa/main recently. Anyway, mach64 is no longer supported by mesa.
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.