I’m trying to use nsight debugging on a really simple program. When i start debugging, application crashes and a window is opened to save dump info.
Sometimes i can see the first frame but no more. Any suggestion or idea?
The program works well without nsight debugging.
Nsight monitor is up and some info is poped up when debbuging connects and disconnects. It seems to works well.
I’m using OGL 4.3, SDL 2.0 and GL3W.
The computer is a laptop MSI i5 - 4210H, GTX850M, 4GB RAM
I got it.
If anybody else has the same problem and a “bug report” maybe.
If i duplicate a visual studio project that works well with nsight, and then i try to debug with the project copy, then nsight wont work.
Can anybody to confirm my theory at other computers?
I have exactly the same problem but with DX11. Start debugging with Nsight → Start Graphics Debugging → App Window pops up → window is opened to save dump info.
Using DirectX 11 and Visual Studio 2012. ‘Working directory’ is set correctly.
System:
Windows 8.1 Pro 64Bit
Core i5 3.1GHz
GTX 760 driver: 347.88
8GB Ram
Visual Studio 2012
Nsight 4.6.0.15071
I do some other tests. I got the error because of nvidia configuration doesnt configure the exe as high performance graphics by default.
In some projects i have it configured (in nvidia control panel) and it worked well, but if i copy the project, the new exe isnt configured (in nvidia control panel). When it is configured correctly then it doesnt crash.
I hope this help you Takatu.
AYan, Is there any way to say to the program that it is a graphics intense program and should be launched by high perf graphics processor?
AFAIK, config it to nvidia control panel is the easiest way, or you can try to plug an extra monitor to your laptop’s external graphics port, that might force activate your dGPU, then you need to render your sample on that monitor to use the dGPU.
@Takatu, your GPU sounds like a standalone version, but not the mobile one for laptop, right?
Yeah, probably, that is the easiest way but im thinking on a general solution, not an adhoc solution. if i launch the program in any computer, graphics card should be the default target.
I had similar issue on my desktop (GTX780, Win10 64bit) and had to disable integrated GPU in the Device Manager to prevent app crashes when starting GPU debugging with NSight. Thanks! The hints here were very helpful.