Difference between revisions of "DebugCSE167F13"
From Immersive Visualization Lab Wiki
| Line 3: | Line 3: | ||
* 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. | ||
* The Curses debugger is a powerful text mode extension of gdb: [http://cgdb.sourceforge.net/ CGDB] | * The Curses debugger is a powerful text mode extension of gdb: [http://cgdb.sourceforge.net/ CGDB] | ||
| − | * | + | * 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]. |
Revision as of 03:35, 26 September 2013
- 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
- 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.
