I have a problem debugging my own applications.
At the same time, the CUDA samples from the SDK compile and debug perfectly on the same machine.
My application was created using the VS wizard as a CUDA 12.5 project.
It compiles and runs through the Nsight Next-Gen VS extension and the breakpoint in the host code is hit fine.
When I start Nsight in the same way in my applicaion, the CUDA threads window appear as expected. The output is the same as for the examples: “Module [CUDA] is loaded. 00000213761ae5c0 Debug_Line: true Debug_Info: true PTX_Line: true PTX_Reg: true PTX_Type: true Name: kernel.cu"
But all breakpoints inside any kernel are grayed out with the message “The breakpoint will not currently be hit…”.
The -G option is set.
The .cu file is defined as CUDA C/C++.
The only difference I have noticed between CUDA Samples and my application is that Samples in VS are running as an x86 application, while mine runs as an x64 application.
No any other significant differences. No errors.
Hi, @micelanholies
Can you share the source code for us to repro ?
As CUDA sdk sample can be compiled and debugged, this seems a specific issue for your code.
Thanks for your reply.
This is not the code issue. The same behaviour on any new project I have create.
What I’ve found - this is the CUDA versions conflict. Hope, the complete reinstall will help.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.