Nsight Visual Studio Ignoring Break Points
Hi, I'm using Visual Studio 2013, Cuda ToolKit v7.5, and Nsight v5.2, and Nvidia GTX 1080. When I start "Cuda Debugging" the Debugger skips all breakpoints, but executes with No errors. I've looked at other thread forums Nvidia, StackOverflow, and also the Nsight v5 manual for HOURS trying to fix the issue with nothing working yet. I did Modify the Properties for the Solution for Debugging (as recommended by the forums) that is included below. The Project is just the sample of what MSVS2013 gives you on start up in Kernal.cu, MSVC2013->NewProject -> CUDA C/C++ -> v7.5. Thanks for the help, Andrew Solution Properties: CUDA C/C++ => Common -> Generate Relocatable Device Code: Yes (-rdc=true) Device -> Code Generation: compute_30,sm_30;compute_35,sm_35;compute_37,sm_37;compute_50,sm_50;compute_52,sm_52; Generate GPU Debug Information: Yes (-G) Generate Line Number Information: Yes (-lineinfo) Verbose PTXAS Output: Yes (--ptxas-options=-v) Host -> Generate Host Debug Information: Yes(-g) CUDA Linker => General -> Generate GPU Debug Information: Yes(-G)
Hi,
I'm using Visual Studio 2013, Cuda ToolKit v7.5, and Nsight v5.2, and Nvidia GTX 1080. When I start "Cuda Debugging" the Debugger skips all breakpoints, but executes with No errors. I've looked at other thread forums Nvidia, StackOverflow, and also the Nsight v5 manual for HOURS trying to fix the issue with nothing working yet. I did Modify the Properties for the Solution for Debugging (as recommended by the forums) that is included below. The Project is just the sample of what MSVS2013 gives you on start up in Kernal.cu, MSVC2013->NewProject -> CUDA C/C++ -> v7.5.

Thanks for the help,
Andrew


Solution Properties:
CUDA C/C++ =>
Common ->
Generate Relocatable Device Code: Yes (-rdc=true)
Device ->
Code Generation:
compute_30,sm_30;compute_35,sm_35;compute_37,sm_37;compute_50,sm_50;compute_52,sm_52;
Generate GPU Debug Information: Yes (-G)
Generate Line Number Information: Yes (-lineinfo)
Verbose PTXAS Output: Yes (--ptxas-options=-v)
Host ->
Generate Host Debug Information: Yes(-g)
CUDA Linker =>
General ->
Generate GPU Debug Information: Yes(-G)

#1
Posted 10/16/2016 12:55 AM   
Hi supracharger, Could you tell me the the windows and driver version? If you use win 10 RS1, I wonder we have internal bug to track it, the Nsight cannot hit bp on win 10 RS1. Best Regards Harry
Hi supracharger,

Could you tell me the the windows and driver version? If you use win 10 RS1, I wonder we have internal bug to track it, the Nsight cannot hit bp on win 10 RS1.

Best Regards
Harry

#2
Posted 10/17/2016 09:58 AM   
Thank you Harry for the help. I am using Windows 10, and Nsight 5.2.0.16268. Please let me know what to do that would help, Thank you, Andrew
Thank you Harry for the help. I am using Windows 10, and Nsight 5.2.0.16268.

Please let me know what to do that would help, Thank you,
Andrew

#3
Posted 10/17/2016 05:53 PM   
Oh, I guess you are using latest windows 10 and driver 373.06, right? Currently nsight doesn't work well with 64-bits apps on win10 red stone with GTX 1080 but the old win 10 is good, we are doing our best to fix it.
Oh, I guess you are using latest windows 10 and driver 373.06, right? Currently nsight doesn't work well with 64-bits apps on win10 red stone with GTX 1080 but the old win 10 is good, we are doing our best to fix it.

#4
Posted 10/19/2016 07:02 AM   
[quote=""]Oh, I guess you are using latest windows 10 and driver 373.06, right?[/quote] Yes, I am using the latest versions of both drivers, just verified. [quote=""]Currently nsight doesn't work well with 64-bits apps on win10 red stone with GTX 1080 but the old win 10 is good, we are doing our best to fix it.[/quote] Would running Visual Studio and Nsight in "Win7 Compatibility mode" fix the problem for the time being in Win10? On another note, Nsight used to work with my GTX 960, but not with the New 1080. Until I re-Installed the Drivers, Cuda Toolkit v7.5 & v8.0, Nsight v5.2, and Graphics Drivers, Da, I wish I didn't do that! Thank you for the help, Andrew
said:Oh, I guess you are using latest windows 10 and driver 373.06, right?

Yes, I am using the latest versions of both drivers, just verified.

said:Currently nsight doesn't work well with 64-bits apps on win10 red stone with GTX 1080 but the old win 10 is good, we are doing our best to fix it.

Would running Visual Studio and Nsight in "Win7 Compatibility mode" fix the problem for the time being in Win10?

On another note, Nsight used to work with my GTX 960, but not with the New 1080. Until I re-Installed the Drivers, Cuda Toolkit v7.5 & v8.0, Nsight v5.2, and Graphics Drivers, Da, I wish I didn't do that!

Thank you for the help,
Andrew

#5
Posted 10/19/2016 07:40 PM   
[quote=""][quote=""]Oh, I guess you are using latest windows 10 and driver 373.06, right?[/quote] Yes, I am using the latest versions of both drivers, just verified. [quote=""]Currently nsight doesn't work well with 64-bits apps on win10 red stone with GTX 1080 but the old win 10 is good, we are doing our best to fix it.[/quote] Would running Visual Studio and Nsight in "Win7 Compatibility mode" fix the problem for the time being in Win10? On another note, Nsight used to work with my GTX 960, but not with the New 1080. Until I re-Installed the Drivers, Cuda Toolkit v7.5 & v8.0, Nsight v5.2, and Graphics Drivers, Da, I wish I didn't do that! Thank you for the help, Andrew[/quote] I think Compatibility mode won't work, but you can have a try, the issue only happens on Pascal card, GTX 960 is a maxwell card and it should work on latest win 10. Sorry for inconvenience, we have several bugs to track the break point issue on win 10 RS1.
said:
said:Oh, I guess you are using latest windows 10 and driver 373.06, right?

Yes, I am using the latest versions of both drivers, just verified.

said:Currently nsight doesn't work well with 64-bits apps on win10 red stone with GTX 1080 but the old win 10 is good, we are doing our best to fix it.

Would running Visual Studio and Nsight in "Win7 Compatibility mode" fix the problem for the time being in Win10?

On another note, Nsight used to work with my GTX 960, but not with the New 1080. Until I re-Installed the Drivers, Cuda Toolkit v7.5 & v8.0, Nsight v5.2, and Graphics Drivers, Da, I wish I didn't do that!

Thank you for the help,
Andrew


I think Compatibility mode won't work, but you can have a try, the issue only happens on Pascal card, GTX 960 is a maxwell card and it should work on latest win 10. Sorry for inconvenience, we have several bugs to track the break point issue on win 10 RS1.

#6
Posted 10/21/2016 09:36 AM   
Hi, I have pretty much the same problem (bp not being hit) with Visual Studio 2015, Cuda 8.0.44, NSight 5.2, drivers 369.30, GTX 1070. Everything seems to work fine but when I start CUDA debugging the monitor opens and then closes immediately , with no error. Thx for any help Stan
Hi,

I have pretty much the same problem (bp not being hit) with Visual Studio 2015, Cuda 8.0.44, NSight 5.2, drivers 369.30, GTX 1070. Everything seems to work fine but when I start CUDA debugging the monitor opens and then closes immediately , with no error.

Thx for any help
Stan

#7
Posted 11/03/2016 11:26 AM   
Scroll To Top

Add Reply