Re: Abnormal execution routine in debugger

jq2000 · ‎07-22-2003

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?

Steven_L_Intel1 · ‎07-22-2003

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

durisinm · ‎07-23-2003

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

Steven_L_Intel1 · ‎07-23-2003

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

gregscvf · ‎07-23-2003

I believe that jq2000 is referring to functional returned values, e.g. sin(...), etc..

Perhaps this should also be on your list also.

Greg

Steven_L_Intel1 · ‎07-23-2003

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

jq2000 · ‎07-29-2003

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.