The GPU debugger in Visual Studio 2012 (VS2012) can be extended by hardware vendors to debug directly on GPU hardware rather than on a software emulator. Nvidia has built such an extension and has made it publicly available as part of Nsight 3.0 (Nsight Visual Studio Edition 3.0 Release Candidate 1 is available here. It requires you to first register and login to the Nsight Visual Studio Edition Registered Developer Program here).
Once you have downloaded the Nsight 3.0 installer, you can follow the instructions below to begin debugging using Nvidia’s GPUs. Debugging on Nvidia hardware requires two machines: one local machine to run Visual Studio and one remote machine (running Windows 7 or Windows 8) with an Nvidia (Fermi or Kepler) GPU to use as a debugging target.
For debugging purposes, because of current limitations in the driver, the remote machine must be configured with only one GPU card enabled.
1. Run the Nsight 3.0 installer on a local machine with an existing VS2012 installation. Once you have accepted the license terms you will be presented with a feature installation summary that looks something like this.
2. Select “Customize” to install the C++ AMP VS extension to VS2012. The custom setup page allows you to individually select those features you want to install. The item you need is “Nsight C++ AMP Debugger”. Select it, hit Next, and let setup continue.
Now that the Nvidia extension is installed you can start debugging an application. The general instructions for remote debugging are in the blog post Remote GPU Debugging in Visual Studio 11. The following changes are required:
In Step 1, you cannot use a Remote Desktop Connection to log into the remote machine, you must log into a display that is physically connected to the machine before you run msvsmon.exe.
In Step 2, you will need to:
Now place your breakpoint, hit F5 and enjoy! Remember that while you are stopped at a breakpoint the GPU is really stopped, so the display will be frozen until you continue.