Run-time error dialog is missing source information

[JannePK]

We updated Intel Visual Fortran from version 11.1.065 to version 2011.6.233 and unfortunately found out that several things have gone worse.

When Run-Time Check Failure occurs with error code 193 in Debug configuration, the dialog is completely missing Routine, Line and Source information. Any idea why's that so??

Other things are:

• default optimization in Release configuration breaks our code
• case sensitivity support has diminished. Lower case "do while"s gave syntax errors

[Anonymous66]

Hello JannePK,

I am confused why the run-time error message for uninitialized variables is listed as something that has gotten worse. It is the same for versions 12.1.0.233 and 11.1.065. Regardless, if you would like it to include more information, I can file a feature request.

There has also been no change in our support for lower case and mixed case source code. I have tested a lower case "do while" statement and it still works. If lower cased "do while" statements are not working in your code, could you upload a sample program that demonstrates this behavior?

Could you also upload your program that is being broken by the default optimization, so I can investigate this issue.

Regards,

Annalee

[JannePK]

Hi Annalee and thanks for your reply.

What comes to the first problem is that, as you can see from the images below, the old version gives you the information of the source code where the error occured (the second image) but the new one doesn't (the first image). Also, when I break the debug session with the old version, I can see the error line in the call stack but its not there with the new version. Therefore there is no way to know where the error occured!?



Above is the error dialog with Intel Visual Fortran Composer XE 2011.


Above is the error dialog with Intel Visual Fortran Compiler 11.1.065.

What comes to case sensibility, if you set Fortran/External Procedurs/Name Case Interpretation to As-is (/names:as_is) in Visual Studio 2008, then lower case "do while"s give syntax errors.

Our program is so large that there is no way to upload it to you, but I try to find time to narrow it down...

[mecej4]

You list the problems but give little information to enable solving them. Which compiler flags do you use? In particular, did you specify /Zi /traceback for the compilation with the new version? Are you compiling for 32-bit or 64-bit Windows? Which OS version?

Since do while is not a procedure, your report of syntax errors suggests that the keywords are incorrectly spelled or there is a non-blank character between the two keywords. Show an example source line or block.

The Intel compilers have been given better error catching abilities with increasing version numbers. Thus, an error that was not caught by the 11.1 compiler may be caught when the new version is used.

[JannePK]

OK, this is the first time I ask support in here so I'm not familiar with your policies yet. I thought these could be some commonly known issues.

Here are the typical compiler options of the IVF-projects:
/nologo /debug:full /Od /stand:f95 /warn:declarations /warn:unused /warn:interfaces /align:sequence /Qzero /names:as_is /module:"Debug\" /object:"Debug\" /Fd"Debug\vc90.pdb" /traceback /check:pointer /check:bounds /check:uninit /check:format /check:output_conversion /libs:dll /threads /dbglibs /c

I made no changes to the projects or to the code when producing the error messages I posted earlier. I just changed the compiler version, rebuilded the solution and ran it.

We use 64 bit Windows 7 Enterprise and Visual Studio Team System 2008 Development Edition. We compile for 32-bit Windows and all Fortran projects are static libs that get linked to main exe.


I'll try to create a small example project to produce the do while error...

I'll also try to narrow the optimization problem to the project that actually causes it.


Thanks for any help in advance!

[Anonymous66]

Thank you for the reproducer. I have escalated this error to our developers. The issue number is DPD200175984.

Regards,
Annalee

[JannePK]

OK, what about the run-time error message problem?

[Anonymous66]

We are planning to include a fix for this issue in a future version which is currently scheduled to be released later this year.

Regards,
Annalee

[Anonymous66]

This is issue has been fixed in Intel® Visual Fortran Composer XE for Windows* 2013 which is now available at the Intel® Registration Center. Regards, Annalee Intel Developer Support * Other names and brands may be claimed as the property of others.