Bug 11016 - glGetVertexAttribivARB(0, GL_VERTEX_ATTRIB_ARRAY_ENABLED_ARB, ...) generates GL_INVALID_ENUM with indirect rendering
Summary: glGetVertexAttribivARB(0, GL_VERTEX_ATTRIB_ARRAY_ENABLED_ARB, ...) generates ...
Status: RESOLVED MOVED
Alias: None
Product: Mesa
Classification: Unclassified
Component: GLX (show other bugs)
Version: 6.5
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: mesa-dev
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-05-21 06:54 UTC by Bruce Merry
Modified: 2019-09-18 17:11 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Testcase illustrating the bug (540 bytes, text/x-csrc)
2007-05-22 00:28 UTC, Bruce Merry
Details

Description Bruce Merry 2007-05-21 06:54:24 UTC
The summary describes the error; I get the same error with other attribute numbers and also GL_VERTEX_ATTRIB_ARRAY_NORMALIZED.

Tracing some code, it appears that indirect_table.c in xorg-server (generated by glX_server_table.py, according to the comment) may be the culprit. It maps GLX opcode 1303 to glGetVertexAttribivNV. The NV and ARB variants use the same GLX opcode, but the NV variant does not support the _ENABLED or _NORMALIZED queries.

I've written a trivial program to illustrate the bug. I'll attach it as soon as I've had an opportunity to restart X in order to test it.
Comment 1 Bruce Merry 2007-05-22 00:28:14 UTC
Created attachment 10068 [details]
Testcase illustrating the bug

It will print "invalid enumerant" if the bug is present, "no error" once it is fixed. Requires GLUT.
Comment 2 GitLab Migration User 2019-09-18 17:11:04 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/51.


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.