The name of the
GLG Terror – Returns an error message
GLG Terror – Returns an error message
( code> void
GlGetError returns the value of the error flag. Each detectable error is assigned a numeric code and a symbolic name. When an error occurs, the error flag is set to the corresponding error code value. No other errors are recorded before the glGetError (return error code) is called, and the flag is reset to GL_NO_ERROR. If a call to glGetError returns GL_NO_ERROR, there are no detectable errors since the last call to glGetError or since GL was initialized.
To allow a distributed implementation, there may be multiple error flags. If any single error flag records an error, it returns the value of the flag and resets the flag to GL_NO_ERROR when you call glGetError. If more than one flag records an error, glGetError returns and clears any error flag value. Therefore, if you want to reset all error flags, you should always call glGetError in the loop until it returns GL_NO_ERROR.
Initially, all error flags are set to GL_NO_ERROR.
The following errors are currently defined:
No errors were recorded. The value of this symbolic constant is guaranteed to be 0.
An unacceptable value was specified for the enumeration parameter. Offending commands are ignored and have no side effects other than setting the error flag.
The number parameter is out of range. Offending commands are ignored and have no side effects other than setting the error flag.
The specified operation is not allowed in the current state. Offending commands are ignored and have no side effects other than setting the error flag.
This command attempts to render to or read from the frame buffer when the currently bound frame buffer is not in the frame buffer complete state (that is, the return value of glCheckFramebufferStatus is not GL_FRAMEBUFFER_COMPLETE). Offending commands are ignored and have no side effects other than setting the error flag.
Not enough memory to execute the command. After recording this error, the state of GL is undefined, except for the state of the error flag.
When the error flag is set, the result of a GL operation is undefined only if GL_OUT_OF_MEMORY occurs. In all other cases, the command generating the error is ignored and does not affect GL state or frame buffer content. If the generate command returns a value, it returns 0.
Copyright © 1991-2006 Silicon Graphics, Inc. This document is licensed under the SGI Free Software B License. See http://oss.sgi.com/projects/FreeB/.
- OpenGL error getting glgeterror ()
- OpenGL step pit record
- C + + uses system (“pause”) to pause black windows
- Python Numpy.ndarray ValueError：assignment destination is read-only
- AE ram preview requires 2 or more frameworks to solve playback
- How to solve runtime error r6016
- BUG: Bad page map in process XXX pte:800000036fae6227 pmd:35be8c067
- Reading and saving opencv Python video
- Save file and exit command of vim
- Flash back after vs compiler running, processing method
- Common problems and basic concept knowledge of OpenGL
- Swap off failed: cannot allocate memory
- (Emitted value instead of an instance of Error) Error compiling template:
- R ggplot Error in .Call.graphics(C_palette2, .Call(C_palette2, NULL)): invalid graphics state
- Error in ffmpeg decoding real-time stream “non existing PPS 0 referenced, decode”_ slice_ header error,no frame!”
- C programming interface of SQLite database (6) result codes and error codes
- Http Error 12057 (Bug Fix Note)
- R language – error analysis – error in Call.graphics (C_ palette2, .Call(C_ palette2, NULL)) : invalid graphics state
- C language write() function analysis: write failed bad address
- Practice — CSS3 — frame animation to achieve special effects