Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
Announcements
FPGA community forums and blogs have moved to the Altera Community. Existing Intel Community members can sign in with their current credentials.
29313 Discussions

No Stack Frame in VS2012 for Debugging

Ben3
Beginner
‎11-08-2012 05:44 PM
671 Views

Hi,

I'm trying to debug an application in the VS2012 debugger but I can't work out how to get the stack frame to display. The call stack just lists things like "cm_mass.exe!<unknown function> Line 162", and it won't show me the contents of any variables. It does hit breakpoints fine and load the appropriate source files. This is the compiler command it's using:

[plain]ifort /nologo /debug:full /Od /QxSSE4.2 /fpp /I"C:\\Users\\bmenadue\\documents\\visual studio 2012\\Projects\\openMP Analysis\\libanalysis\\x64\\Debug" /Qopenmp-report1 /warn:all /debug-parameters:all /assume:byterecl /module:"x64\\Debug\\" /object:"x64\\Debug\\" /Fd"x64\\Debug\\vc110.pdb" /FAs /Fa"x64\\Debug\\" /traceback /check:all /libs:dll /threads /dbglibs /c /Qvc11 /Qlocation,link,"C:\\Program Files (x86)\\Microsoft Visual Studio 11.0\\VC\\bin\\amd64" "C:\\Users\\bmenadue\\Google Drive\\Code\\openMP Analysis\\trunk\\bin\\cm_mass.f90"[/plain]

It's definitely using /traceback and /debug:full with no optimisation. I was originally using openMP as well (and set the reentrancy using /reentrancy:threaded), but I removed them in case that was breaking the debugger (but it didn't help).

Thanks,

Ben

EDIT: Fixed the command line because the forum gobbled up the backslashes.

0 Kudos

Link Copied

1 Reply
Steven_L_Intel1
Employee
‎11-08-2012 07:01 PM
671 Views
Seems to work ok for me in a sample project (not using OpenMP, though - that probably causes problems with examining variables as it can't see into the threads.)
0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.