Difference between revisions of "DebugCSE167F13"

Latest revision as of 11:20, 25 October 2013

General OpenGL Debugging Tips:

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.
The Curses debugger is a powerful text mode extension of gdb: CGDB

For GLSL Shader Development:

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.

@@ Line 1: / Line 1: @@
+General OpenGL Debugging Tips:
 * 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://www.opengl.org/sdk/docs/man2/xhtml/gluErrorString.xml gluErrorString()] to parse the error message.
 * There is a [http://www.opengl.org/wiki/Common_Mistakes web page on common OpenGL mistakes].
 * For debugging under Linux, the command line debugger [http://sourceware.org/gdb/current/onlinedocs/gdb/ gdb] and the GUI wrapper around it [http://www.gnu.org/s/ddd/manual/html_mono/ddd.html 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.
 * The Curses debugger is a powerful text mode extension of gdb: [http://cgdb.sourceforge.net/ CGDB]
+For GLSL Shader Development:
 * If your shader code builds but won't use the shaders, and you are using Linux and a laptop with hybrid graphics systems, try [https://github.com/MrMEEE/ironhide/ Ironhide].