Difference between revisions of "DebugCSE167F11"
From Immersive Visualization Lab Wiki
(New page: * 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/onli...) |
|||
| (One intermediate revision by one user not shown) | |||
| Line 1: | Line 1: | ||
| + | * 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/man/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]. | * 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. | * 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. | ||
| + | * Christian recommends a powerful text mode extension of gdb called [http://cgdb.sourceforge.net/ 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 [https://github.com/MrMEEE/ironhide/ Ironhide]. | ||
Latest revision as of 20:37, 4 November 2011
- 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.
