Intel FORTRAN 7.0.13 problems...
-
I don't know how many people in this forum use the FORTRAN compiler from Intel, but we just encountered a nasty problem that doesn't seem to be documented. When debugging in VS .NET 2003, an error appears that reads, "FORTRAN run-time error. Deallocate error 492: Variable is not allocated. End of diagnostics." This happens whether the code is C++ or FORTRAN, whether or not breakpoints are set. I have been able to reproduce this on another, totally different system. If I trace through the code one line at a time, the execution reaches line 463 in crt0dat.c, which is "ExitProcess( status );" The variable "status" exists, and the value is valid. Has anyone else seen this error? I thought it might be worth posting here, while I try to get in touch with Intel's technical support division. Thanks! -- Paul "I drank... WHAT?"
-
I don't know how many people in this forum use the FORTRAN compiler from Intel, but we just encountered a nasty problem that doesn't seem to be documented. When debugging in VS .NET 2003, an error appears that reads, "FORTRAN run-time error. Deallocate error 492: Variable is not allocated. End of diagnostics." This happens whether the code is C++ or FORTRAN, whether or not breakpoints are set. I have been able to reproduce this on another, totally different system. If I trace through the code one line at a time, the execution reaches line 463 in crt0dat.c, which is "ExitProcess( status );" The variable "status" exists, and the value is valid. Has anyone else seen this error? I thought it might be worth posting here, while I try to get in touch with Intel's technical support division. Thanks! -- Paul "I drank... WHAT?"
I filed a support case with Intel on this issue, and apparently they already knew about it! The problem has been in their issue tracking system for a while, but hasn't been solved. So they were able to reproduce it, and escalate the issue to a higher level. Now here's a silly question: How can a piece of software be released, through multiple revisions, with such a glaring hole??? You can't debug ANY native code without VS.NET 2k3 crashing! How that ever got through Intel's Q/A is beyond me... -- Paul "I drank... WHAT?"