Nsight EE do not support debug several applications concurrently.
You may get below info when you launch another debugging
cuda-gdb failed to grab the lock file /tmp/cuda-dbg/cuda-gdb.lock.
Another CUDA debug session (pid 16319) could be in progress.
Are you sure you want to continue? (y or [n]) [answered N; input not from terminal]
If you really want to do this, may you can debug from cuda-gdb command line. Just launch 5 cuda-gdb session.
But we can’t promise the debug result is OK as everything may happen when you use 1 GPU to do so many things.
Do you mean the result of nvvp is incorrect?
I run the following command and generate 5 xxx.nvprof files at the same time.
After that, I can see kernels launched from different processes on nvvp.
I’m confused here.
You said you want to debug 5 applications.
But here the command is to profile. The command to profile is OK. And the profile result should be correct.
I want to know how does the GPU handle multiple kernels?
Does the GPU do exclusive control of the kernel?
If GPU can run multiple kernels without using stream simultaneously, is it running like a Round-Robin?
Because I confirmed that the variation of kernel execution time became large when multiple kernels were launched for a single GPU.
And I visualized the kernels by nvcc.
As a result, launched kernels were not processed one by one but were run at the same time.