On Apr 30, 6:48=A0pm, Steve Lionel <steve.lio...@[EMAIL PROTECTED]
> wrote:
Thanks. And yessir, even with /traceback (already on) and /
check:pointer, still failing at run-time.
Declared as an allocatable,
if (not(allocated(grid_dat%zg))) then
write(*, '(/1x, "ALLOCATE_GRID: grid coordinates, allocating
grid_dat%zg")')
allocate(grid_dat%zg(idim, jdim), stat =3D allocerr)
if (allocerr /=3D 0) stop 3
endif
Or as a pointer,
if (size(grid_dat%zg)=3D=3D0) then
write(*, '(/1x, "ALLOCATE_GRID: grid coordinates, allocating
grid_dat%zg")')
allocate(grid_dat%zg(idim, jdim), stat =3D allocerr)
if (allocerr /=3D 0) stop 3
endif
Regardless, allocate is failing with the following command line
feedback,
forrtl: severe (157): Program Exception - access violation
Image PC Routine Line Source
ntdll.dll 7C911E58 Unknown Unknown Unknown
ntdll.dll 7C918251 Unknown Unknown Unknown
ntdll.dll 7C911C76 Unknown Unknown Unknown
lodi.exe 00B1C521 Unknown Unknown Unknown
Which has to do with something like RtlInitializeCriticalSection(),
deep within NTDLL.DLL. Not especially productive (i.e. no resolution
to the issue) here, however thanks all for the insight, really and
truly. Next place to go appears to be into the Intel Fortran forums.
That said, I can't say this doesn't have something to do with a
programmatic issue elsewhere in the code. That's entirely possible
(i.e. scientists having written the code before we inherited it).
Nothing against scientists, mind you, but there's something to be said
about a professional developer's awareness of memory management
issues.
Anywho... Neither here nor there, apart from the fact we've got to get
through the consequences of said issues, of course...
> Michael wrote:
> > After taking out the stat from allocate, we get further, but we still
> > end up failing, same place in NTDLL.DLL.
>
> No, you're failing in your application. =A0Try adding /traceback to the
> set of options, so you get more detailed information, and you might also
> try /check:pointer.
>
> If you need more help, post in the Intel Fortran user forum or contact
> Intel sup****t (links below).
>
> I am not aware of any bugs related to ALLOCATABLE in the version you are
> using.
> --
>
> Steve Lionel
> Developer Products Division
> Intel Cor****ation
> Nashua, NH
>
> For email address, replace "invalid" with "com"
>
> User communities for Intel Software Development Products
> =A0 =A0http://softwareforums.intel.com/
> Intel Fortran Sup****t
> =A0 =A0http://sup****t.intel.com/sup****t/performancetools/fortran
> My Fortran blog
> =A0 =A0http://www.intel.com/software/drfortran
|
