Table of Contents - gDEBugger GL Tutorial
Getting Started
- Installation and Startup
- Creating Your Project
- Simple Tasks
- gDEBugger usage tips
- How do I clean up my OpenGL usage?
- How do I find unneeded OpenGL function calls in my code?
- How do I measure my application's performance?
- How do I optimize my OpenGL application performance?
- How do I peer inside OpenGL?
- How do I know which execution mode to use?
Debug Mode
- The Main Window
- Debugging Tasks
- Locate OpenGL Errors
- Locate Detected Errors
- View Graphic Memory Information
- Locate Graphic Memory Leaks
- View the effect of OpenGL function calls on draw buffers (Draw Functions)
- Find Unrecommended Function Calls
- View Textures and Buffers Information
- View Shaders and Shading Programs' Information and Edit Shaders "On the Fly"
- Work with OpenGL State Variables
- Work with Breakpoints
- View Statistical information about OpenGL usage
- Locate Software Fallbacks
Profile Mode
- The Main Window
- Profiling Tasks
- Work with performance counters
- Locate Graphic Pipeline bottlenecks
Analyze Mode
- The Main Window
- Analysis Tasks
- View State Change Statistics
- Locate Redundant State Changes
- View Deprecated Function Statistics and Make Your Application Forward-Compatible
- View Redundant State Change, Get and Deprecated Functions' Chronological Position in the Frame Rendering Process
Additional Information
- Execution Modes comparison
- Glossary
- State Variable
- Redundant State Change
- OpenGL Error
- Detected Error
- Graphic Memory Allocated Object
- Graphic Memory Leak
- Vertex Batch
- Deprecated Function, Deprecated Feature
- Function Types
- Forced Mode
- Raster Mode
- Software Fallback
- Frame Terminator
- Keyboard Shortcuts