I was able to run the visual profiler on the BoxFilter example from the SDK. But when I run my code, the profiler fails. The processing ran as expected (I implemented a simple image inversion, nothing fancy)
I think the problem comes from the fact that my CUDA code does not run in the same context as the SDK examples. I get 2 symptoms:
CUDA running in a DLL which is loaded by an application through LoadLibrary: no profiler data is generated
CUDA running in an application which uses MFC: “Program run #1 failed, exit code:2”
In any case I suspect that there are restrictions when using CUDA with DLL’s (I’ve had other problems in the past).
Anyway I’ll try to extract my CUDA code and insert it into one of the SDK’s examples and profile it from there. I hope this gets eventually fixed though.
I am not sure my message will help you, but I am in the same situation. I have the error “no data rows in profiler output file” when I’m trying to use the Visual Profiler with my application. My CUDA program is included in a DLL called by an AVISynth script. I dont think the problem comes from some restrictions between CUDA and DLL using, because I ve previously succeeded to profile another DLL with the visual profiler.
I’ve set environnment variables CUDA_PROFILE = 1, but the generated file does not contain any data.
However i’ve noted that if I set CUDA_PROFILE = 1 in Project options (properties>debugging>environnment), and launch the program directly from Visual Studio, then the log file generated (in sources folder) contains all the informations !
I’m using CUDA 2.2 and visual sutdio express 2008.