Open topic with navigation

In NVIDIA® Nsight™ Visual Studio Edition, the host is the term for the computer that is running Visual Studio, where your application is being built and debugged. After you install NVIDIA Nsight on your computer, you will see a new menu called Nsight on your Visual Studio taskbar.

Feel free to explore the various options on this menu. The items that are critical for debugging will be discussed in further detail in later topics.

Nsight Host Settings

After installing NVIDIA Nsight on the host machine, open Visual Studio and go to Nsight > Options to configure your settings.

1. On the General page, configure some of the basic options such as timeouts, whether to enable secure connections, and which port NVIDIA Nsight should use to connect to the target machine.
   Note that the default port setting is 8000. The port number on both the host and target machines must match in order for a successful connection to occur. (See Target Basics for more information.)
   
   
   
   
2. On the Analysis page, you can configure several analysis options such as CUDA kernel trace mode, default activity type and timeline axis mode, as well as a default report directory.
   
   
   
   
3. On the CUDA page, you can configure several options for both the CUDA Debugger as well as the CUDA Memory Checker.
   
   
   
   
4. On the Debugger page, configure some basic display options for NVIDIA Nsight.
   
   
   
   
5. On the Graphics page, you will find the following options:
   
   
   1. Frame Debugging: Force Present/SwapBuffer calls on the target to repaint the window - If this option has been set to True, the frame replay will automatically invalidate the window of the target application for every Present/SwapBuffer call.
   2. Shader Debugging: Debug All Shaders - This option selects whether to instrument all shaders to be debugged. If you set this to false, it may improve the performance of your application, if you are only setting breakpoints in a small subset of shaders. However, doing this may also cause certain features (such as debugging of sympathetic shader threads) to be unavailable.
   3. Shader Debugging: Preferred remote shader debugging mode - With this option, you can choose whether to prefer full hardware debugging or replay-based debugging on remote targets. When a breakpoint is hit, replay-based debugging frees the GPU to draw the desktop or run other application code. Full hardware debugging halts the GPU when a breakpoint is hit; no other tasks may run, but the debugger may run faster and may provide deeper insight of the hardware state.
   4. Shader Debugging: Show disassembly if source does not exist - With this option, if no source can be found for the given shader, then disassembly will be shown instead. You can choose one of three options here: Ask, Always show, or Never show.
      
6. On the Updates page, select whether or not you want NVIDIA Nsight to automatically search for updates upon startup.
   
   
   
   

Click OK when you are finished configuring your options for NVIDIA Nsight.

Configuring NVIDIA Nsight on the Host Machine

After NVIDIA Nsight has been installed on the host machine, it will need to be configured. To do this:

1. Open your project in Visual Studio.
2. On the Solution Explorer menu, click the Nsight User Properties icon. (As an alternative, you can also go to the Project menu > Nsight User Properties.)
   
   
   
3. This will open the NVIDIA Nsight User Settings dialog box.
   
   
   
   
4. Under connection name, specify the name of the computer that will be your target machine.
   The default setting is localhost; however, unless you are using a local debugging configuration, you'll need to enter the remote computer's name.
   
   You can also use the Nsight Connections toolbar to specify the name of the computer that should be used for running the target application.
   
   
   
5. For Launch external program, enter the file path to the application that is being debugged.
   
6. Click the Synchronization page.
   
   
   
   From here, you can choose which file extensions to include or exclude for synchronization purposes.
   If you're debugging a large application, you'll want to turn off synchronization to prevent performance problems.
   
   

   When using file synchronization, all file paths are relative to localhost. When file synchronization is turned off, the file path is relative to the target machine (which could be localhost as well, depending on your settings.)

7. Click the Shader Compilation page.
   
   
   
   This page allows you to specify include paths for compiling the shaders in your application.

Open topic with navigation