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 on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.

Using MS2005 VS Debugger

Reeves__Nathan
Beginner
695 Views
I have the debugger working, and I have created a break point and the this is reached by the debugger. However, i can only see the values of the variables that are defined locally and not globally.

I am not a Fortran expert, but I am use to using the debugger in C. In C, you can hover teh mouse Icon above any variable that is in scope and the value is displayed (and memory address), and you can set up a watch to look at variables that are in scope.

Can this be done in Fortran using the MS Debugger ?

Thanks,
Nathan
0 Kudos
2 Replies
ArturGuzik
Valued Contributor I
695 Views
Quoting - nathanreeves
I have the debugger working, and I have created a break point and the this is reached by the debugger. However, i can only see the values of the variables that are defined locally and not globally.

I am not a Fortran expert, but I am use to using the debugger in C. In C, you can hover teh mouse Icon above any variable that is in scope and the value is displayed (and memory address), and you can set up a watch to look at variables that are in scope.

Can this be done in Fortran using the MS Debugger ?

Thanks,
Nathan

Hi,

I believe it will depend (a lot) on which version you're using. The capabilities changed (improved) over the years and versions.

If you can't see module variables, the ModuleName::VariableName (typed in Watch window) always worked.

A.
0 Kudos
Steven_L_Intel1
Employee
695 Views
In the current version (11.1) you can view module variables that are used in the current routine the same as locals. For module variables that are not used, you can use the modname::varname syntax as Artur says.
0 Kudos
Reply