From: Vladimir D. <vo...@mi...> - 2005-08-01 19:11:44
|
Hi all, I am getting the following segfault with recent checkout of Mesa (as of few seconds ago) and R300 driver: ----------------------------------------------------------------------- Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1211504128 (LWP 16041)] 0xb7b9fe78 in attrib_1_4 (v=0x1300) at tnl/t_vtx_generic.c:100 100 ATTRS( 1 ) (gdb) bt #0 0xb7b9fe78 in attrib_1_4 (v=0x1300) at tnl/t_vtx_generic.c:100 #1 0xb7b9e63f in choose_1_4 (v=0x1300) at tnl/t_vtx_api.c:464 #2 0xb7ba124a in _tnl_VertexAttrib4fvARB (index=136238856, v=0x1300) at tnl/t_vtx_generic.c:479 #3 0xb7b7a6ea in neutral_VertexAttrib4fvARB (index=1, v=0x1300) at vtxfmt_tmp.h:458 #4 0x0804b59b in init () #5 0x0804c07e in main () ----------------------------------------------------------------------- This appears to be internal to the Mesa and I have run out of obvious things to check. For some reason the variables v and index get their values screwed up repeatedly and, furthermore, attrib_1_4 gets too far with unmodified index (still at too high value). Any suggestions ? This is with gcc 3.3.6 thank you ! Vladimir Dergachev |