OpenGL Error Codes: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
Better listing and wiki-fication. |
||
| Line 1: | Line 1: | ||
'''Error Codes''' returned by <code>glGetError()</code>: | |||
* GL_INVALID_ENUM: given when an enumeration parameter contains an enum that is not allowed for that function. | |||
* GL_INVALID_VALUE: given when a numerical parameter does not conform to the range requirements that the function places upon it. | |||
* GL_INVALID_OPERATION: given when the function in question cannot be executed because of state that has been set in the context. | |||
* GL_STACK_OVERFLOW: given when a stack pushing operation causes a stack to overflow the limit of that stack's size. | |||
* GL_STACK_UNDERFLOW: given when a stack popping operation is given when the stack is already at its lowest point. | |||
* GL_OUT_OF_MEMORY: given when performing an operation that can allocate memory, when the memory in question cannot be allocated. | |||
* GL_TABLE_TOO_LARGE (if the optional imaging subset (GL_ARB_imaging) is supported) | |||
* GL_INVALID_FRAMEBUFFER_OPERATION | |||
[[Framebuffer Objects]] have their own error codes for codes for testing framebuffer completeness. The meaning of these codes is defined in the [[Framebuffer Objects#Framebuffer Completeness|section on framebuffer completeness]]. | |||
Revision as of 02:06, 30 December 2009
Error Codes returned by glGetError():
- GL_INVALID_ENUM: given when an enumeration parameter contains an enum that is not allowed for that function.
- GL_INVALID_VALUE: given when a numerical parameter does not conform to the range requirements that the function places upon it.
- GL_INVALID_OPERATION: given when the function in question cannot be executed because of state that has been set in the context.
- GL_STACK_OVERFLOW: given when a stack pushing operation causes a stack to overflow the limit of that stack's size.
- GL_STACK_UNDERFLOW: given when a stack popping operation is given when the stack is already at its lowest point.
- GL_OUT_OF_MEMORY: given when performing an operation that can allocate memory, when the memory in question cannot be allocated.
- GL_TABLE_TOO_LARGE (if the optional imaging subset (GL_ARB_imaging) is supported)
- GL_INVALID_FRAMEBUFFER_OPERATION
Framebuffer Objects have their own error codes for codes for testing framebuffer completeness. The meaning of these codes is defined in the section on framebuffer completeness.