i keep receiving an error while profiling my code :
Error: application being profiled returned a non-zero return code …
I am not sure what the problem is. The Code is healthy and memcheck returns o errors. Why is this happening? I have been able to profile the same code before i switchied into Cuda 5.5 rc …
On most operating systems a non-zero process exit code indicates an error in the application. The Visual Profiler is warning that it detected a non-zero process exit code from the target application.
Does the target application return a non-zero process exit code when run outside of the Visual Profiler? If yes, then fix the target application.
Does the target application return a non-zero process exit code only when launched from the Visual Profiler? If yes, then debug what error is occurring in the application. These types of errors are often cause by a difference in the process launch environment including but not limited to:
Incorrect working directory
Incorrect command line arguments
Incorrect environment variables
These three settings can be specified in the Visual Profiler session settings.
Thank you for your rely, I have already solved this problems.Actually I installed cuda 8 and cuda tookit 8, but may be a wrong environment setting is made. Thank you for your kind help
yuan-ubuntu:
How to solve the problem?
I have a problem same as you.
the error message is “The application being profiled returned a non-zero return code”
I already debugged my code.
but when I use the nvvp, that error occurs…
Thank you for your reply.
It already fed into the main routine. (i.e., return 0 is fed into the main code)
So, you guess that problem is the application exiting part, right?
I found a reason for the problem.
A part of my code needs ‘sudo mode’.
So when I execute the code root mode, it works.
but when I execute the code user mode, it doesn’t work.
Do you know the how to execute sudo mode at the nvvp?
issue lies in the fact that you are returning something other than 0 “return 0;” in your code for the program to exit or simply in the settings you are trying to run your .cu file when you should be running the .exe file generated on compilation. For me, it was the latter that fixed it.