I’m very familiar with Nsight basics but I left out one important detail…
Nsight is incorrectly reporting an error in a kernel earlier in my kernel pipeline and I’m unable to debug any kernel after that point.
How do I know it’s an incorrect false positive error? I can never say there aren’t bugs in a kernel, but the Debug and Release kernels run correctly outside of Nsight. Stream synchronization is used immediately after the kernel launch to check for errors.
Furthermore, the error is also reported as a global memory access error on lines that access shared memory. For this reason I’m skeptical that Nsight isn’t inducing the error.
This keeps me from debugging the kernel I’m interested in and the end result is, “You can’t get there from here.”
I’d really like to focus on a kernel like I can in the profiler:
I’m on Win10x64/361.60/7.5/VS2013.