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

trouble in release mode

kooka
Beginner
914 Views

I have a trouble in the release mode when i try to open some file. But when i try it indebug mode all works perfectly, so i dont understand why. the error message is the following:

fortrtl:severe(157): Program Exception - access violation

image pc routine line source
cpf.exe 00401FA9 DIBUJARAPOYOS 174 apoyos.f90
cpf.exe 004048b9 dibujarviga1 294 dibujoviga.f90
cpf.exe 00406413 refreshwindow 676 dibujoviga.f90
cpf.exe 0046502f abrir 528 abrir.f90
cpf.exe 004f3a0c unknown unknown unknown
cpf.exe 00501f20 '' '' ''
user32.dll 7e398734 '' '' ''
....
....
cpf.exe0049cfe2 framewndproc 608 initialsettings.f90
...

tanks for your help

0 Kudos
4 Replies
anthonyrichards
New Contributor III
914 Views
Try adding IMPLICIT NONE everywhere and look for uninitialised variables (debug may initialise variables to zero whereas release does/may not).

0 Kudos
kooka
Beginner
914 Views
Quoting - anthonyrichards
Try adding IMPLICIT NONE everywhere and look for uninitialised variables (debug may initialise variables to zero whereas release does/may not).


this line is causing me the problem.


CALL DIBUJARAPOYOS(i,apoyo)

Icheked all the subroutines involved and i have implicit none in all of them so i really dont know. thanks for the ansdwer
0 Kudos
Les_Neilson
Valued Contributor II
914 Views
Quoting - kooka

this line is causing me the problem.


CALL DIBUJARAPOYOS(i,apoyo)

Icheked all the subroutines involved and i have implicit none in all of them so i really dont know. thanks for the ansdwer

(1) What are the definitions of "i" and "apoyo" ? Presumably "i" is a scalar integer ? and apoyo real scalar/array ?
(2) Do the dummy arguments of the subroutine DIBUJARAPOYOS match "i" and "apoyo" from the calling routine ?

Unfortunately this kind of error can be caused by code earlier in the process and only manifest itself at a later point. I would suggest you turn ondiagnostic checking, both compile time and run time (at least array and string bounds and uninitialised variables) Also generate interface blocks and check interfaces.

Les
0 Kudos
bmchenry
New Contributor II
914 Views

i would suggest checking all properties (options) in debug v release mode.
ignore the 'debug' type options but check for default type options.
It is probably a default 'initialize to zero' type option (Fortran->Data dialog)
an easyway to check debig v release is to open 2 instances of your project
one set to debug, one set to release
walk through all the property dialogs in Project -> [project] properties dialogs displaying each side by side.
you can also simply open the project as text file and check ALL settings.
0 Kudos
Reply