Difference between revisions of "DebugCSE167F12"
From Immersive Visualization Lab Wiki
(New page: * If you suspect an error in your OpenGL code, try using the [http://www.opengl.org/sdk/docs/man/xhtml/glGetError.xml glGetError()] command to find the location of the error, then [http://...) |
Latest revision as of 01:30, 27 September 2012
- If you suspect an error in your OpenGL code, try using the glGetError() command to find the location of the error, then gluErrorString() to parse the error message.
- There is a web page on common OpenGL mistakes.
- For debugging under Linux, the command line debugger gdb and the GUI wrapper around it ddd are among the most popular debugging tools, both of which allow tracing through C++ code step by step and displaying the content of variables.
- Christian recommends a powerful text mode extension of gdb called CGDB, perhaps just the right medium ground between command line and GUI.
- Tip by Kristian: If your shader code builds but won't use the shaders, and you are using Linux and a laptop with hybrid graphics systems, try Ironhide.
