Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
29274 Discussions

Abnormal execution routine in debugger

jq2000
Beginner
‎07-22-2003 05:46 PM
1,040 Views
Sometimes, when I used debugger to trace Fortran code, value of parameters and execution routines are ridiculous. It seems that actual execution routine is different from what show in debugger. Even after I clean all projects and delete all .LIB files then rebuild the projects, the problem is still there. include/lib link under "VC++ - Tools - Options - Directories" were set to correct pathes. What factors could cause this type of problem? How can I solve it?
0 Kudos

Link Copied

6 Replies
Steven_L_Intel1
Employee
‎07-22-2003 05:54 PM
1,040 Views
What compiler and version are you using? I've seen this behavior with old CVF versions in particular situations, but not the current version. Also, you can see this if you've enabled optimization.

Steve
0 Kudos
Copy link
durisinm
Novice
‎07-23-2003 02:49 PM
1,040 Views
When you mention "parameters" are you talking about Fortran PARAMETERs or arguments to functions and subroutines? As far as I know, CVF has never been able to display the values of PARAMETERs in the debugger (although I'm not sure why), but I've never had a problem with arguments.

Is there a way to see the values of PARAMETERs with the debugger? It sure would be helpful to me with some programs.

Mike
0 Kudos
Copy link
Steven_L_Intel1
Employee
‎07-23-2003 05:18 PM
1,040 Views
The debugger knows only about variables. PARAMETERs are "named constants". The compiler would have to create "pretend" variables for them in order for the debugger to see them. It's on our long list of things we'd like to do.

Steve
0 Kudos
Copy link
gregscvf
Beginner
‎07-23-2003 07:54 PM
1,040 Views
I believe that jq2000 is referring to functional returned values, e.g. sin(...), etc..

Perhaps this should also be on your list also.

Greg
0 Kudos
Copy link
Steven_L_Intel1
Employee
‎07-23-2003 08:19 PM
1,040 Views
Greg, I was responding to Mike's question.

Regarding jg2000's question - I didn't think it was about intrinsics such as sin. But a sample would be helpful. My guess is that "parameters" in this context means routine arguments.

Steve
0 Kudos
Copy link
jq2000
Beginner
‎07-29-2003 02:43 AM
1,040 Views
Sorry to respond late.
"Parameter" I mentioned is a routine argument or normal variable, not Fortran PARAMETER. I should have not used this terminology.
The compilers I used are VC++6.0 and CVF 6.6B.
After set Optimization from "Minimum*" to "None", the debugger works as expected.
Thank you for all your advice.
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.