Ogldebug Overview

Ogldebug Overview

The ogldebug tool helps you find OpenGL programming errors and discover OpenGL programming style that may slow down your application. After finding an error, you can correct it and recompile your program.

Using ogldebug, you can perform the following actions at any point during program execution:

Create a history ("trace") file of all OpenGL calls made. The history file is legal C code and may be compiled and run, letting you experiment with calls to find bugs or try test cases.
Set a breakpoint at all occurrences of a given OpenGL call.
Step through (or skip) OpenGL calls.
Find out about OpenGL errors.
Display information about OpenGL state, current display lists, and the window that belongs to the application you're debugging.

Note: If you're debugging a multi-window or multi-context application, ogldebug starts a new session (a new window appears) when the application starts a new process. The process ID is displayed in the title bar for each new window. Note that the OpenGL debugger isn't a general-purpose debugger. Use dbx and related tools such as cvd (CASEVision/Workshop Debugger) to find problems in the non-OpenGL portions of a program.

How ogldebug Operates
Setting Up ogldebug
Using a Configuration File