NVIDIA® Nsight™ Development Platform, Visual Studio Edition 3.2 User Guide
Send Feedback
Make sure that the modules you intend to debug are built with the compiler generating debug symbols. If a module has no symbols, then debugging is disabled for all functions in that module.
NOTE: You cannot debug CUDA code in a target process while simultaneously debugging the x86 code of the same process.
Use a separate Visual Studio instance to debug the host portion of a target application. If you wish to debug the host portion of your CUDA application while the CUDA Debugger is attached, you must attach using a different Visual Studio instance. Attaching the same instance of Visual Studio to debug both the host portion and the device portion of a target application will cause the debuggers to conflict. The result is that the target application and the CUDA Debugger hang while being blocked by operations of the native debugger.
The NVIDIA Nsight tools support launching and debugging a program on a single system. Please see System Requirements for Nsight Software for more information. Please also refer to the Setup Local Debugging topic for configuring a debugging setup with multiple GPUs.
localhost
.
You can launch and debug a program on any properly configured remote host. Please see How To: Install the Nsight Monitor and Setup Remote Debugging for more information on how to install and configure the NVIDIA Nsight tools on your remote machine.
localhost
with the name of your target machine (the remote computer where the application to be debugged will run).
WRONG:M:\
CORRECT:jsmith.mydomain.com
NOTE: You cannot simultaneously perform CUDA debugging and x86 debugging of the same process.
NVIDIA® Nsight™ Development Platform, Visual Studio Edition User Guide Rev. 3.2.131009 ©2009-2013. NVIDIA Corporation. All Rights Reserved.