| Summary: |
arbvptest3 segfaults because of bad index to tnl->vtx.tabfv |
| Product: |
Mesa
|
Reporter: |
Tilman Sauerbeck <tilman> |
| Component: |
Mesa core | Assignee: |
mesa-dev |
| Status: |
RESOLVED
FIXED
|
QA Contact: |
|
| Severity: |
normal
|
|
|
| Priority: |
high
|
Keywords: |
patch |
| Version: |
git | |
|
| Hardware: |
x86 (IA32) | |
|
| OS: |
Linux (All) | |
|
| Whiteboard: |
|
|
i915 platform:
|
|
i915 features:
|
|
| Attachments: |
Don't add VERT_ATTRIB_GENERIC0 to the indices
|
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.
0x00000000 in ?? () (gdb) f 1 #1 0xb7960627 in _tnl_VertexAttrib3fARB (index=19, x=1, y=0.5, z=0.25) at tnl/t_vtx_generic.c:472 472 tnl->vtx.tabfv[index][3-1]( &z ); (gdb) p index $1 = 19 _tnl_VertexAttrib3fARB (and other functions in t_vtx_generic.) have the following code snippet: if (index >= MAX_VERTEX_ATTRIBS) index = ERROR_ATTRIB; else index += VERT_ATTRIB_GENERIC0; MAX_VERTEX_ATTRIBS == VERT_ATTRIB_GENERIC0 == 16, and tabfv only has 17 slots, so this doesn't make sense. The segfault happened with the r300 driver, but it doesn't seem to be driver specific.