gDEBugger is an advanced OpenGL and OpenCL Debugger, Profiler and Memory Analyzer. The application does what no other tool can - lets you trace application activity on top of the OpenGL and OpenCL APIs and see what is happening within the system implementation.
gDEBugger helps you optimize OpenGL and OpenCL applications performance. It saves you the time required for locating "hard to find" OpenGL and OpenCL related bugs and helps you improve application quality and robustness.
gDEBugger assists you to improve application performance and quality, reduce debugging and profiling time, shorten "time to market", deploy on multiple platforms, conform with future OpenGL and OpenCL versions, optimize memory consumption
NOTE: After installing, fill in the registration information to get a free one-year license.
Here are some key features of "gDEBugger GL":
· View Windows OS, NVIDIA, AMD (ATI) and S3 GPUs performance counters as bars as performance graphs
· Locate graphic pipeline performance bottlenecks using a powerful performance toolbar
· Edit and continue GLSL shaders "on the fly"
· Break on OpenGL errors, gDEBugger's detected errors, memory leaks, redundant state changes and more
· View the application's graphic memory consumption broken down into individual OpenGL objects
· View OpenGL static buffers, framebuffers, pbuffers and textures as an image or "raw data"
· View the OpenGL calls history
· Use gDEBugger's Analyze mode to analyze and view OpenGL usage and performance warnings specific to your application
· Perform regression tests to understand changes in visual display, performance and accuracy between different versions of your OpenGL based application
Requirements:
· All OpenGL versions up to 3.2 are supported
· OpenCL version 1.0 and version 1.1 are supported
What's New in This Release: [ read full changelog ]
· OpenCL 1.1 is now supported by gDEBugger CL
Changed:
· Improved the OpenCL forced / disable modes, the modes now retain the driver overhead and synchornization effects, and only lower the actual workload
· Added a cap to the number of debug and output strings reported, as applications using many of them at high frequency could cause the gDEBugger client application to respond slowly or even hang
Fixed bugs:
· When using rectangular (non-square / cube) OpenCL images, the bytes read, bytes written and bytes copied counters would display wrong values
· Using functions which take matrix or vector parameters would sometimes result in crashes if two such functions were called concurrently from two rendering threads
· Fixed a rare crash in multi-threaded applications
· In some configurations, the gDEBugger OpenGL and OpenCL servers would crash as the debugged application exited
· Some applications would experience crashes if the time difference between a context's creation and the first draw function c...
Find us on Google+
