Download CUDA Debugger

Event Notifications
The kernel event notification policy is controlled with kernel_events and
kernel_events_depth options.
‣
(cuda-gdb) set cuda kernel_events none
Possible options are:
none
no kernel, application or system (default)
application
kernel launched by the user application
system
any kernel launched by the driver, such as memset
all
any kernel, application and system
‣
(cuda-gdb) set cuda kernel_events_depth 0
Controls the maximum depth of the kernels after which no kernel event notifications
will be displayed. A value of zero means that there is no maximum and that all
the kernel notifications are displayed. A value of one means that the debugger will
display kernel event notifications only for kernels launched from the CPU (default).
In addition to displaying kernel events, the underlying policy used to notify the
debugger about kernel launches can be changed. By default, kernel launches cause
events that CUDA-GDB will process. If the application launches a large number of
kernels, it is preferable to defer sending kernel launch notifications until the time
the debugger stops the application. At this time only the kernel launch notifications
for kernels that are valid on the stopped devices will be displayed. In this mode, the
debugging session will run a lot faster.
The deferral of such notifications can be controlled with the
defer_kernel_launch_notifications option.
‣
(cuda-gdb) set cuda defer_kernel_launch_notifications off
CUDA_GDB receives events on kernel launches (default).
‣
(cuda-gdb) set cuda defer_kernel_launch_notifications on
CUDA-GDB defers receiving information about kernel launches
set cuda defer_kernel_launch_notifications option is deprecated and has no
effect any more.
www.nvidia.com
CUDA Debugger
DU-05227-042 _v6.0 | 34