I have a host machine that runs Ubuntu 18.04 LTS natively and remotely connects to Jetson Xavier. When I execute a simple CUDA program, it runs fine, but when I attempt to do visual profiling I get some version of the following error:
“Application received signal”
“Application received signal 139”
The entire program is aborted and I’m left with no profiling graphs or data.
In the remote debugging settings, upload the executable to Jetson Xavier and run the program.
The program simply prints “Hello CPU” from the main() function, and “Hello GPU” from a CUDA kernel (using a global function).
If I take out the CUDA kernel and cudaDeviceReset(), I am able to profile with no problem. It shows CPU profiling data and graphs.
If I take out only cudaDeviceReset(), the program doesn’t even recognize the CUDA kernel. It shows CPU profiling data and graphs.
I’ve tried checking and unchecking “Enable concurrent kernel profiling” but that doesn’t change anything
I’ve tried checking and unchecking “Start application with profiling enabled” but that doesn’t change anything.
I’ve tried checking and unchecking the “Unified memory” setting but that doesn’t change anything.
There is talk of a segmentation fault. There is also talk of it being a combination of two errors (11 + 128), but no real information on how to go about resolving them.
I really need to be able to profile my applications, especially the GPU side of the equation. Any help would be appreciated.