Till now, after many trials with many graphics cards, the only thing Shader Debugger can do is spit out all kinds of strange errors.
- Windows 7 Professional, SP1, Build 7601
- Windows 10 Education, version 1803, Build 17134.48
- Quadro K600
- CUDA 9.1
- Nsight 5.5
- Visual Studio 2015 Update 3 version 14.0.25431.01
The code to be debugged is the first OpenGL example of the Red Book “OpenGL Programming Guide: The Official Guide to Learning OpenGL, Version 4.5 with SPIR-V (9th Edition)” with minor modification that should be irrelevant to the problem. I am debugging under remote mode and following instructions in the documentation regarding how to use Shader Debugger. On both machines, Nsight Monitor is run as Administrator.
If I use Machine 1 as host and Machine 2 as target, the error is that I cannot set the breakpoint. This is what I got after clicking the gutter of VS’s editor:
If I use Machine 2 as host and Machine 1 as target, the error changes to “Unable to launch because architecture type is Unknown. (System.InvalidOperationException)” at launch:
I was told that Shader Debugger works with Kepler cards. But the two Quadro K600’s are both Kepler, why are there still so many errors? How to fix? Is it true that only GK104 and GK106 can work with Shader Debugger? If so, under what version of Nsight and Windows? Looking forward to your help. Thank you.
PS: I didn’t impose any special configuration on the environment, so you can reproduce these errors without asking me for the OpenGL code (unless you insist).