Nsight Eclipse profile error Nsight Eclipse profile error in ubuntu

Hi all,
I have a problem on profiling in Nsight Eclipse.
Although I added nvprof path to PATH environmental variable,
when I try to profile, profile perspective is opened however
it doesn’t work since the error:
Unable to run application. org.eclipse.core.runtime.CoreException: unable to find nvprof.

I will be appreciated if you can help me.

Thanks in advance


I don’t know if you had a response but I have the same problem. I can launch a profiling using the terminal but not in nsight. I have the same error message. if someone could help me it will be wonderful.



I don’t know if you resolved your problem but I found a solution. There is an executable file, nvvp in usr/local/cuda/bin. You have just to run nvvp in the terminal and it opens NVIDIA Visual Profiler. After that you have just to enter the file you want to profile (test.x) and the software runs and profiles your program.

I hope it will help you.

How do you start Nsight? Are you typing “nsight” in the shell or double-click the launcher script in the file manager?

It was not possible to run IDE in any way other then from the shell in CUDA 5.0 preview release. We updated the launcher script in the upcoming release and it is now possible to start the IDE by double-clicking the launcher script in /usr/local/cuda/bin.

This is how the script looks like now:
PATH=$PATH:/usr/local/cuda-5.0/bin LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/cuda-5.0/lib:/usr/local/cuda-5.0/lib64 UBUNTU_MENUPROXY=0 LIBOVERLAY_SCROLLBAR=0 /usr/local/cuda-5.0/libnsight/nsight


I created a shortcut for nsight. So it was like calling from terminal. What I did is writing a script that you provided above and It worked.

Now another problem arised. Profiler gives error:

“Some collected events or source-level results could not be associated with the session timeline. This may prevent event, metric, and source-level results from being assigned to some kernels.”

Anyway, thanks all of you four your help.

Take a look at the online Visual Profiler User’s Guide (Help menu -> Help Contents). There are some sections on “Application Requirements” and “Profiling Limitations” that might be interesting for you. Also, there are have been some fixes since the preview that will be available in the upcoming RC that might lessen or resolve the issue for you.