Bug 17407 (glGetString) - Invocation of the interface glGetString between glBegin and glEnd does not generate GL_INVALID_OPERATION error
Summary: Invocation of the interface glGetString between glBegin and glEnd does not ge...
Status: RESOLVED MOVED
Alias: glGetString
Product: Mesa
Classification: Unclassified
Component: Mesa core (show other bugs)
Version: 6.4
Hardware: Other Linux (All)
: medium normal
Assignee: mesa-dev
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-02 04:29 UTC by Artak Petrosyan
Modified: 2019-09-18 20:21 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description Artak Petrosyan 2008-09-02 04:29:05 UTC 
The standard states:
"GL_INVALID_OPERATION is generated if glGetString is executed between the execution of glBegin and the corresponding execution of glEnd.", but invocation of the interface glGetString(GL_VERSION) between glBegin and glEnd does not generate GL_INVALID_OPERATION error.
Comment 1 Roland Scheidegger 2008-09-02 07:20:26 UTC 
I think this is due to indirect rendering/glx. __indirect_glGetString uses a local cache and doesn't check for this error itself. Not sure though how to fix...
Comment 2 GitLab Migration User 2019-09-18 20:21:57 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/957.

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.