It is certainly expected that you can launch and profile applications directly using both the ncu command line as well as the ncu-ui GUI with the Interactive Profile activity on Windows 10. This is the default option for the CLI flag --mode, named launch-and-attach.
In your first post, you mentioned this was on Manjaro Linux. Later you mentioned your Ubuntu workflow work properly, but your latest question is about a problem on Windows 10. Can you please clarify on which platform you are having the issue right now?
This is the line where it blocks (right at the begining of the code)
HANDLE_ERROR( cudaMallocManaged((void**)&m_block , sizeof(uint64_t)) );
Whether I start using “Interactive Profile” or “Profile” … it doesn’t matter. It doesn’t go beyond the
When you say it blocks there, you mean it doesn’t even fully connect in interactive mode, right? I.e. it doesn’t show you the first CUDA API call in the API stream view tool window, like here ? Instead, it keeps showing the connection log that you mentioned in your first post?
I truly don’t see why it would behave like this, especially since you say that launching from the CLI and attaching from the UI works for you, which is essentially the same underneath. This seems to imply there aren’t any conceptual errors with how you application behaves that Nsight Compute can’t handle, and the relevant ports are accessible. Still, it would be good if you could try a small CUDA sample app as well, to see if that behaves better.
One thing that appears to be different is that you mentioned your ncu --mode launch command was run as administrator, but when trying to launch from the UI, the UI process wasn’t, correct? Can you check the following:
- try profiling directly from the CLI in a non-admin console, i.e. ncu .
- try profiling directly from the CLI in an admin console, i.e. ncu .
- try launching interactively from the UI, when the UI itself is started as admin