I am using Parallel Studio XE 2016 Update 1 in Visual Studio 2010 Professional SP1 on Windows 10 Professional 64-bit.
If I place a breakpoint in the block between PROGRAM and END [PROGRAM] (I have only the specification and executable part, no CONTAINS) and run the 64-bit debugger, one of two scenarios happens:
- Visual Studio crashes.
- If I disable the breakpoint, let the console application hit another breakpoint in a subroutine, and re-enable the breakpoint, the debugger stops running and it opens a tab "No Source Available (No symbols are loaded for any call stack frame. The source code cannot be displayed.)". The call stack window is empty and it is possible to continue the run by pressing F5. I remember this behavior from earlier versions of Parallel Studio XE and I always switched to the 32-bit debugger that has never had this problem.
Re-installing Parallel Studio did not help. Is there anything I can try to be able to stop the 64-bit debugger using breakpoints in the main program?