Nsight 调试出现Parallel Nsight Debug CUDA grid launch failed: CUcontext: 211577632 CUmodule: 223878456

本文链接：https://blog.csdn.net/bslance/article/details/22205333

今天进行单机Nsight调试时出现了local debugging failed,Nsight is incompatible with Aero desktop.接着换了一个电脑主题（非Aero模式）后问题又接着出现了，CUDA kernel debugging is disabled ,breakpoints will not be hit in any kernel,Enable kernel debugging with Nsight/options/CUDA/CUDA debugger/Enable kernel launch debugging,按照提示更改了Options之后又出现了问题：CUDA grid launch failed,CUcontext:29715464 CUmodule:39436344 Function;_z9addkernelPipkis1

Parallel Nsight CUDA Debugger
------------------------------------------------------------------------------

The application being debugged with the Nexus CUDA debugger, was unable to
find any associated source. This could be for a number of reasons:

1) CUDA has not been initialized.
Make sure cuInit has been called, and it returned a successful result.

2) No CUDA contexts have been created.
Once a context is created, memory can be examined in the context. Each context
shows up as a single "Thread" in the Visual Studio Threads view. (Debug | Windows | Threads)

3) There are no active CUDA grids in any context.
A grid must be launched in order to hit breakpoints.

4) You have selected the "Default Context" in the Visual Studio Threads view.
This context is a placeholder shown when there are no available actual CUDA
contexts. It does not show real data.

5) No CUDA modules have been loaded.
You can see which modules are loaded in each CUDA context by showing the
Visual Studio Modules view. (Debug | Windows | Modules)

6) Symbolics were not found for the loaded .cubin.
The module needs to be built with debug information. Please specify the
-G0 switch when building.

7) A grid launch failed while running a kernel.