Hi @892516165
Can you continue the debugging session after this warning is printed? This can be a normal cusparse library behavior (it’s expected to have CUDA_ERROR_NO_BINARY_FOR_GPU during the library initialization):
- without the debugger, this error is handled by
cusparse - when running with
cuda-gdbthe debugger would intercept and report this error
Similar issue: Nsight Compute get stuck at cusparse function calling: CUDA_ERROR_NO_BINARY_FOR_GPU(209) - #4 by jmarusarz