nsight

CUDA: Passing parameters to host compiler during Nsight session

被刻印的时光 ゝ 提交于 2019-12-24 15:34:28
问题 I have a cuda (v4.2) program running under visual studio 2010, to which I pass various command line parameters. I want the host compiler to see the same parameters when I run through nsight (v2.2). I assume I have to do this via (right click project) -> nsight user settings->command line arguments, but haven't yet managed to find a syntax that doesn't crash nvcc. I'm assuming it's arranged around "--run-args " somehow? ** Clarification, after comment below: Sure when you debug straight

How to debug (GLSL) shaders using Nsight?

时光总嘲笑我的痴心妄想 提交于 2019-12-24 10:26:41
问题 How can I debug glsl shaders using Nsight? I am using Nsight Visual Studio Edition 5.2. I've tried using Nsight Visual Studio Edition 5.1. These both don't work. What I mean is that I've tried using this method and it doesn't work: Open Visual Studio Project Select "Nsight" from Menu and "Start Graphics Debugging" Let the program run for a while Press "Ctrl+Z" Press "Space" Go to "API Inspector" in Visual Studio Select "Program" from left side bar Select a "Source" from "Linked Shader State"

cuda-gdb not working in nsight on linux

亡梦爱人 提交于 2019-12-24 08:31:30
问题 I installed cuda 5 in my Ubuntu 12.10 and it is working well, I can compile and debug through cuda-gdb in terminal as well. I'm trying to use nsight, it compiles and executes my code with no issues, but when I try to debug I got the following error Error in final launch sequence Failed to execute MI command: -gdb-set cuda api_failures ignore Error message from debugger back end: Undefined set cuda command: "api_failures ignore". Try "help set cuda". Undefined set cuda command: "api_failures

debugging cuda files in visual studio

[亡魂溺海] 提交于 2019-12-24 02:08:28
问题 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

Include a static cuda library into a c++ project

北慕城南 提交于 2019-12-23 06:58:39
问题 I have a templated static CUDA library which I want to include into a common c++ project. When I include the headers of the library the compiler crashes and says It cannot resolve the CUDA-specific symbols. Of course the g++ compiler cannot interpret these symbols. I know the problem, but I do not know how to fix this problem using the nsight IDE. I'm using nsight for both, the cuda/nvcc library and the c++/g++ project. Console output: make all Building file: ../src/MedPrak.cpp Invoking: GCC

CUDA debugging with VS - can't examine __restrict__ pointers (Operation is not valid)

帅比萌擦擦* 提交于 2019-12-23 04:37:15
问题 I have a simple kernel, in which I'm allocating some space using malloc, simply as: __global__ void chainKernel() { float* __restrict__ boo = (float*)malloc(sizeof(float)); *boo = 0; *boo = *boo + 100; return; } If I put a breakpoint on *boo = *boo + 100 I can't see the contents of *boo. Instead I get Operation is not valid due to the current state of the object next to the variable in the debugger window. If I remove the __restrict__ however, the value is shown correctly. Is this normal

Nsight skips (ignores) over break points in VS10 Cuda works fine, nsight consistently skips over several breakpoints

喜夏-厌秋 提交于 2019-12-22 06:39:46
问题 I'm using nsight 2.2 , Toolkit 4.2 , latest nvidia driver , I'm using couple gpu's in my computer. Build customize 4.2. I have set "generate GPU ouput" on CUDA's project properties, nsight monitor is on (everything looks great). I set several break points on my global - kernel function . nsight stops at the declaration of the function , but skips over several break points. it's just like nsight decide whether to hit a break point or skip over a break point. The funny thing is that nsight

Can't “Attach to Process” to debug using Nsight in Visual Studio 2008

可紊 提交于 2019-12-21 20:57:34
问题 I'm trying to debug a cuda application using Nsight with Visual Studio 2008, so I opened the Attach to Process dialog. I set the Transport to be Nsight GPU Debugger. I set the Qualifier to the name of my machine (MONAD in this case). I see a list of processes in the Available Processes widget, but they are all greyed out, and if I click on my application, it remains greyed out and I cannot click the attach button. When I built the application I made sure to use the -G0 flag when compiling my

CUDA Parallel NSight Debugging host and device simultaneously

偶尔善良 提交于 2019-12-20 06:26:36
问题 Does anyone know if its possible to Debug CUDA using parallel NSight on a remote machine? I am able to step into CUDA code but not my host code. It says CUDA has the capability to generate host debug information so debugging remotely and locally should be possible. My card is a 580 GTX. //device code <-- able to debug device code //host code <---- when device code returns, should be able to debug host code Thanks! 回答1: Simultaneous GPU/CPU debugging from a single IDE instance is unfortunately

nsight eclipse remote debugging timed out error

瘦欲@ 提交于 2019-12-20 06:24:55
问题 I have a Server running CentOS 6.0 and I'm trying to use it as a remote host for cuda debugging. In order to do this, I installed cuda-toolkit 5.5 both on the server and my notebook, which is running ubuntu 12.10 OS. I configured the two machines as the NVIDIA-cuda-instruction told me, yet when I started the Nsight eclipse edition and tried to remote debug my cuda applications, I ran into error, whcih says: Failed to execute MI command: -target-select remote 192.168.2.105:2345 Error message