Re: problem with unhandled exception (acces violation) and undefined array/pointer
- From: Steve Lionel <steve.lionel@xxxxxxxxxxxxx>
- Date: Mon, 18 May 2009 16:33:37 -0400
kuco wrote:
„I:\x\source.f(666) : Warning: In the call to READ, actual argument
#22 does not match the type and kind of the corresponding dummy
argument.
2 A(K17),A(KADD1),A(KADD2),A(KADD3),A(KADD4),A(KADD5) ,A
(KADD6))“
Fortran requires that the data type (e.g. REAL, INTEGER) and kind (double precision, (4), etc.) match that of the corresponding dummy argument in the routine being called. You are using Intel Visual Fortran which, by default, will warn you about such mismatches.
From what you write later, it seems that these mismatches were intentional, so the warnings could be ignored, though some kinds of mismatches may lead to other problems.
When I run the code it goes until the the point that the warning
message is indicating. It enters the subroutine but fails when the
problematic varsiable is used for the first time. The code stops
without any error message.
My guess is that there is an error message, but it's in the console output window which is behind the debugger window. In order to help you further, we'd need to know what that error message said. I'm going to take a wild guess and say that it's an array bounds error.
--
Steve Lionel
Developer Products Division
Intel Corporation
Nashua, NH
For email address, replace "invalid" with "com"
User communities for Intel Software Development Products
http://software.intel.com/en-us/forums/
Intel Fortran Support
http://support.intel.com/support/performancetools/fortran
My Fortran blog
http://www.intel.com/software/drfortran
.
- References:
- Prev by Date: Re: problem with unhandled exception (acces violation) and undefined array/pointer
- Next by Date: Re: Precision of literal real constants, parameters, and Fortran standard
- Previous by thread: Re: problem with unhandled exception (acces violation) and undefined array/pointer
- Index(es):
Relevant Pages
|