When I have Max 5 running, even with no patch loaded, and then I start the debugger in Visual Studio my Windows XP SP3 system crashes to a black screen and I need to force shut down the computer and restart.
Even if the program being debugged is a trivial do-nothing command line application, and Max has been freshly started with nothing loaded the same thing happens.
There is not a problem if I run the same trivial program without VS running, nor if I run the trivial program in VS in non-debug mode.
If I set a breakpoint at the start of main() in the program it is never reached before the crash.
ANY program that I try to debug in VS gives the same result even if the program has nothing to do with Max. Also, the same crash happens if I attach the debugger to any already running process.
Has anyone else seen this problem?
- Chris Graham
Well, I think the problem may be the Max copy protection. The Visual Studio debugger works when run at at the same time as the Max runtime.
I’m not sure it it’s the dongle or the copy protection in general.
Is there any other way to debug externals with the Max full version available at the same time?
Would it help to install my development system’s Max and authorize it with the challenge/response system rather than the dongle?
Sorry, but you can only debug in the runtime version. There’s no other
C74 RSS Feed | © Copyright Cycling '74