I think I found a bug of injection/hook module in nsight target package.
target application build by cuda toolkit 10.1, visual studio 2017.
nsight compute ui reports such an error in “Profile” Mode.
“profiler returned an error code: 3765269247”
but the app only does a simple check and return.
gpuErrchk(cudaSetDevice(0)); gpuErrchk(cudaGetDeviceProperties(&deviceProp, 0)); printf("GPU Device %d: \"%s\" with compute capability %d.%d\n\n", 0, deviceProp.name, deviceProp.major, deviceProp.minor); return true;
in interactive profile mode after resume first cuda api break, profiling ui disappears immediately.
test with Cuda 10.1 sample “simplePrintf”, launch from cli.bat gave same result:
“E:\Program Files\NVIDIA Corporation\Nsight Compute 2019.3.1\nv-nsight-cu-cli.bat” -o profile simplePrintf.exe
==ERROR== The application returned an error code (3765269347)
==WARNING== No kernels were profiled
==WARNING== Profiling kernels launched by child processes requires the --target-processes all option
and demo suite in 10.1 toolkit have same error after first cuda api call.
profiling on normal windows without cuda api call doesnt cause such a 3765269347 error (maybe hook mechanism havn’t trigged).
2019.3.0 and 2019.3.1 gives same error.
but these application working fine without profiler.
and I can profiling them in nsight system (with cuda options checked).
my os: windows 10 enterprise LTSC 2019, x64
ram: 128GB, with ECC
vga card: zotec RTX2070Super 8G pgf OC