Difference between revisions of "Debugging Tools"

From OpenGL Wiki
Jump to navigation Jump to search
 
m
Line 2: Line 2:
  
 
=== GLIntercept ===
 
=== GLIntercept ===
−
Download from http://glintercept.nutty.org<br>
+
Download from http://glintercept.nutty.org
−
This is free and also open source, for Windows. You need to install it which will create a folder C:\Program Files\GLIntercept0_5 for version 0.5. The folder will have a few gliConfig.ini (gliConfig_AuthorStd.ini, gliConfig_ExtOverride.ini, etc) that are basically example INI files for you to study and understand what you can do with this tool. In the same folder, you will find a fake OpenGL32.dll. Drop the DLL and your INI in the folder of your EXE and run your EXE. All function calls will go through the fake DLL and this is how GLIntercept detects if your program generated an error, if it called a GL function when there was no GL context, if your program is leaking resources. You can configure it so that it dumps a file when you press ctrl+shift+8. The XML files shows all the GL functions called, which ones generated a problem, the texture used, the shader used. The program also generates a log file with information on any problems detected.<br>
+
 
−
<br>
+
'''Description:'''
−
Cons: The program is intended for applications that have a single GL context.<br>
+
GLIntercept is a free open sourced program intended for Windows platforms. After installing, a folder (<code>C:\Program Files\GLIntercept*_*</code> where the asterisks are the version numbers) will have been created. This folder holds several samnple configuration files of interest which can be used to configure GLIntercept: <code>gliConfig.ini</code>, <code>gliConfig_AuthorStd.ini</code>, <code>gliConfig_ExtOverride.ini</code>, etc. In addition, this folder holds a version of the <code>OpenGL32.dll</code> file which acts an intermediary between your system's OpenGL implementation and GLIntercept. To utilize this functionality, copy the DLL and a customized copy of the <code>gliConfig.ini</code> file to your application's target folder (usually where the .EXE resides) and run your application. All invoked OpenGL function calls will route through the DLL, allowing GLIntercept to detect:
−
<br>
+
 
−
More to come.
+
* Errors
 +
* Function calls before context creation
 +
* Resource leaks
 +
 
 +
You may configure GLIntercept to output log files (upon pressing [Ctrl]+[Shift]+[8]) showing all of the OpenGL functions called, problems and used shaders and textures.
 +
 
 +
'''Cons:''' The program is intended for applications that have a single GL context.
 +
 
 +
[[Category:General OpenGL]]

Revision as of 16:15, 23 August 2008

There are several tools that can aid in the debugging of your OpenGL program.

GLIntercept

Download from http://glintercept.nutty.org

Description: GLIntercept is a free open sourced program intended for Windows platforms. After installing, a folder (C:\Program Files\GLIntercept*_* where the asterisks are the version numbers) will have been created. This folder holds several samnple configuration files of interest which can be used to configure GLIntercept: gliConfig.ini, gliConfig_AuthorStd.ini, gliConfig_ExtOverride.ini, etc. In addition, this folder holds a version of the OpenGL32.dll file which acts an intermediary between your system's OpenGL implementation and GLIntercept. To utilize this functionality, copy the DLL and a customized copy of the gliConfig.ini file to your application's target folder (usually where the .EXE resides) and run your application. All invoked OpenGL function calls will route through the DLL, allowing GLIntercept to detect:

  • Errors
  • Function calls before context creation
  • Resource leaks

You may configure GLIntercept to output log files (upon pressing [Ctrl]+[Shift]+[8]) showing all of the OpenGL functions called, problems and used shaders and textures.

Cons: The program is intended for applications that have a single GL context.

Retrieved from "http://www.khronos.org/opengl/wiki_opengl/index.php?title=Debugging_Tools&oldid=1760"