Hi David, thank you for the timely response :) Yes, I’ve been having some troubles trying to get the debugger work.
I am using GeForce RTX 2060 with 436.15 driver, CUDA 10.1.243 and Optix 6.5.
I built Optix 6.5 SDK using Cmake 3.14.5; I checked “CURA_NVRTC_ENABLED” for JIT compilation and specified “-lineinfo” and “-G” flags in “CUDA_NVRTC_FLAGS”. Otherwise the CUDA compiler flags were left untouched, and with the addition of the above-mentioned flags:
Then I ran one of the samples (“optixSphere”) in the Debug mode to inspect the state of CUDA compiler options - everything appears in order, as specified in the Cmake GUI. Finally, I received the following message in the console:
OptiX Error: 'Unknown error (Details: Function "_rtProgramCreateFromPTXString" caught exception:
Compile Error: Unknown Value when trying to figure out pointer space for ray payload argument to rt_trace at: [ i64 %3 ])
If I don’t specify the debug flag “-G”, then the application runs and I can indeed break & inspect the device state, as you said. Namely, CUDA threads launch information, i.e. “threadIdx”, “gridDim” and the state of GPU registers. Although I am afraid I can not say that at the moment I am confident navigating this information, hence I was hoping to generate a friendlier debug output.