gDEBugger does not stop on the breakpoints I defined.
gDEBugger displays a message saying “Cannot Debug Kernel”.
What are the (software and hardware) system requirements to run gDEBugger?
What are the differences between gDEBugger for Visual Studio and the gDEBugger standalone application?
What are the “Frame terminators”?
Which OpenCL and OpenGL extensions are supported?
Which OpenCL and OpenGL version is supported?


gDEBugger does not stop on the breakpoints I defined.

Check if the Breakpoint checkbox in the Breakpoints dialog (Alt+Shift+B) or Breakpoints view is checked.

gDEBugger displays a message reading “Cannot Debug Kernel”

The most probable reasons for this issue are listed below:

Cause of error Possible workaround
Using dated drivers / gDEBugger version Verify that you have the latest version of AMD Catalyst and gDEBugger installed
Atomic operations that return a value are not currently supported. Affected extensions include: cl_khr_int64_base_atomics, cl_khr_int64_extended_atomics, cl_khr_global_int32_base_atomics, cl_khr_global_int32_extended_atomics, cl_khr_local_int32_base_atomics, cl_khr_local_int32_extended_atomics, cl_ext_atomic_counters_32 and cl_ext_atomic_counters_64. Split kernels that use atomic operations into a separate program from those kernels that do not use atomic operations. This will allow debugging of the kernels that do not use atomic operations.
Debugger could not allocate memory. Debug application as a 64 bit application to provide greater process memory resources. If this is not possible, try to reduce host memory usage and fragmentation. Alternatively, try to enqueue smaller global work sizes.
Kernel argument type may not be supported for debugging by driver. Remove const, __readonly and __writeonly qualifiers from kernel arguments.

What are the (software and hardware) system requirements to run gDEBugger?

Please have a look at the System requirements page for all software requirements.

gDEBugger supports API-level debugging on all hardware that can run OpenCL or OpenGL

gDEBugger supports kernel debugging on OpenCL-enabled AMD GPUs with appropriate drivers.

What are the differences between gDEBugger for Visual Studio and the gDEBugger standalone application?

All capabilities available in either version are also available in the other one.

gDEBugger for Visual Studio uses as much of Visual Studio’s native controls and views as possible, to make the debugging experience more natural to Visual Studio users.

The gDEBugger standalone application brings all of gDEBugger’s capabilities to users who can’t or do not want to use Visual Studio – Linux users and Windows users using other development IDEs.

What are the Frame terminators?

Frame terminators are the functions that end your application render and computation frames. gDEBugger use the frame terminators for frame per second measurements, statistics analysis, marking and clearing stream loggers logs, performance counters sampling and more.

Which OpenCL and OpenGL extensions are supported?

Please have a look at our Supported Extensions page.

Which OpenCL and OpenGL versions are supported?

gDEBugger currently supports all OpenCL versions up to version 1.2 and OpenGL versions up to version 3.2.