- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
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
Link Copied
2 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.

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