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

Unhandled Exception - Access Violation with ifort 2013

afcalderncsu_edu
Beginner
841 Views

Hi all,

Is there any significant behavioural changes between ifort 12 and 13?  I get an Unhandled Exception / Access Violation if I run an executable compiled with Intel Visual Fortran Composer XE 2013 Update 1 13.0.3600.11 and Visual Studio 2012.  This was not the case with Intel Visual Fortran Composer XE 2011 Update 12 12.1.3537.2010 and Visual Studio 2010.  I did not change any of the source code.  I am just trying to rebuild and test.  It's not allowed for me to share any of the source code, so it makes it difficult for me post any code.  However I did record a video (http://work.adancalderon.net:8888/intel/UnhandledException-AccessViolation.mp4) showing how the code crashes.

Thanks for reading,

Adan Calderón

0 Kudos
5 Replies
Steven_L_Intel1
Employee
841 Views

Yes, there are hundreds if not thousands of significant changes between the versions. But that isn't going to help you.

I suggest you debug the application and see where it is failing. You may have a coding error that went undetected in the older version.  Be sure to turn on full run-time checking as well as "Check Routine Interfaces" under Diagnostics. You may also find my article Don't Touch Me There - What error 157 (Access Violation) is trying to tell you helpful.

0 Kudos
mecej4
Honored Contributor III
841 Views

If your code contains errors of the type that cause access violations, it should be no surprise that the code builds and runs with no apparent errors with certain compiler versions/options, but fails spectacularly with other versions/options.

A video of the program crashing may have some entertainment value to some, but for the purpose of finding the causes it is as useful as a panoramic photograph of a car wreck would be to find if/why the brakes failed and caused the car to crash.

0 Kudos
Le_Callet__Morgan_M
841 Views

Thank you.

Are you aware of any change in calling convention on the c++ side.

Indeed when trying to call a dll I get an access violation error.

0 Kudos
Steven_L_Intel1
Employee
841 Views

There are no changes in calling convention.

0 Kudos
Le_Callet__Morgan_M
841 Views

I posted in in the wrong thread but i got my answer. Thank you.

0 Kudos
Reply