cuda vs 断点_在Visual Studio中调试cuda文件

最新推荐文章于 2024-10-17 10:52:43 发布

曹永露

最新推荐文章于 2024-10-17 10:52:43 发布

阅读量650

点赞数

文章标签： cuda vs 断点

本文链接：https://blog.csdn.net/weixin_30775883/article/details/111918931

版权

在Visual Studio中，当尝试使用断点调试从cpp转换为cuda(cu)文件的函数时，遇到无法查看变量的问题。尽管能够暂停执行，但“错误符号未找到”。解决方案是使用Parallel Nsight Visual Studio Edition，这是一个适用于Windows的设备代码调试工具，可以指导如何附加到运行中的进程进行调试。

摘要由CSDN通过智能技术生成

i have a cpp function (function.cpp") which i "mex"-ed. then i open the function.cpp file in visual studio and attach visual studio to a running matlab process.

when i call the function in matlab i am able to set breakpoints in the function.cpp file and step through it observing the variables.

The debugging process breaks down when i change the function to a cuda file (function.cu). Following the process described above i am still able to stop within function.cu but i cannot see any variables. when i try to "watch" a variable it says "Error symbol .. not found"

i have nsight installed in visual studio. question: how can i observe my variables in the file function.cu in the debug mode as i do for the function.cpp file. Is this possible ?

Note that the function.cu is not in a project. it is just a standalone file with cpp code of a function (say somefunction(){}). for debugging purpose i am opening it up in visual studio. i am compiling the function.cu file in matlab using "nvmex -g wrapper.cu" the wrapper.cu is a matlab mexfunction wrapper which makes calls to somefunction() written inside function.cu

解决方案

You're using the VS debugger which is a host debugger, so it doesn't know how to debug device programs. To debug device code in Windows you should look at Parallel Nsight Visual Studio Edition.

You can search the docs for a guide to attaching to a running process, for the current release (2.2) the specific page is here.