- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am running Windows 7 Professional SP1 64-bit, the Fortran version is Intel Visual Fortran Compiler XE 12.0.4.196, I am using Visual Studio 2008. My problem is that I am not able to do normal, in-solution debugging.
Whenever I place a breakpoint in the code, the execution stops, but when I click "Show Next Statement" or press Alt+Num*, the yellow arrow indicating the next statement does not occur and I get the warning instead: "No symbols are loaded for any call stack frame. The source code cannot be displayed."
I thought the problem could be related to parallelization, but disabling parallel calculation in my application did not help. I tried rebuilding the application, but it did not help either.
This is happening when I use Debug and x64. Debug and Win 32 are fine and debugging works well. The two configurations are completely the same, the only difference is the platform.
Whenever I place a breakpoint in the code, the execution stops, but when I click "Show Next Statement" or press Alt+Num*, the yellow arrow indicating the next statement does not occur and I get the warning instead: "No symbols are loaded for any call stack frame. The source code cannot be displayed."
I thought the problem could be related to parallelization, but disabling parallel calculation in my application did not help. I tried rebuilding the application, but it did not help either.
This is happening when I use Debug and x64. Debug and Win 32 are fine and debugging works well. The two configurations are completely the same, the only difference is the platform.
Link Copied
1 Reply
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I tried to duplicate your problem with the same compiler version but on Win 7 Home Premium X64 SP1. Had no problems locating the stop location in the source.
Suggestion: try a project with at least two source files. Set a breakpoint and run. When the breakpoint is hit, open the source file other than the one with the breakpoint line, and try clicking the yellow arrow on the Debug toolbar. You should find yourself back in the other window and on the breakpoint line.
Suggestion: try a project with at least two source files. Set a breakpoint and run. When the breakpoint is hit, open the source file other than the one with the breakpoint line, and try clicking the yellow arrow on the Debug toolbar. You should find yourself back in the other window and on the breakpoint line.
Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page