Debugging CUDA MEX in VS2017 on Volta GPU

Question

Aaron Meldrum 2019-3-14

0
链接

此问题的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/450099-debugging-cuda-mex-in-vs2017-on-volta-gpu

评论： Vyacheslav Samokhvalov 2021-3-19

I’m using Visual Studio 2017 Professional version 15.9.2, MATLAB R2018b, and I’m running a Titan V in TCC mode, driver version 411.70.

I’m attempting to debug a CUDA MEX function to solve a ‘CUDA_ERROR_ILLEGAL_ADDRESS’ error I’m getting. My code compiles fine, and runs for a set number of repetitions, then produces this error.

Starting with this post as a reference

https://www.mathworks.com/matlabcentral/answers/88541-failed-to-attach-matlab-in-visual-studio-2010-in-order-to-debug-cuda-kernel

It seems some things have changed since this question was answered.

I can follow the procedure outlined by Joss up to step 12. ‘Transport’ appears to have been replaced by ‘Connection Type’, and ‘NSight GPU Debugger’ seems to be showing up as ‘NSight VSE Debugger(Legacy)’. However, at this point I’m unable to locate MATLAB in the Processes for CUDA type (nothing at all shows up, actually).

If I right click the .CU file in Visual Studio and choose ‘Debug and Launch Settings’ then I see that “Default” is selected.

In researching this on my own, it seems the “Legacy” debugger does not support my GPU.

https://developer.nvidia.com/nsight-visual-studio-edition-supported-gpus-full-list#SupportedComputeConfigs

and it seems that attachment to a process is not possible using the next gen debugger

https://docs.nvidia.com/nsight-visual-studio-edition/Content/Attach_CUDA_to_Process.htm

Does this mean that im out of luck for debuggers in mexcuda until NSight Next Gen Debugger is updated? Is there an alternative process I should be following? Is there something I'm missing?