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

Debugging Fortran 11 in Windows 7

Pablo_Guerron
Beginner
780 Views
Hi,
The debugger (Fortran 11 Windows 7 (64 bit)) crashes when running the following code:
open (unit = 11,file = 'dataqe.txt')
do i = 1,204
read (11,'(3f24.17)') ourdata(:,i)
enddo
close (11)
I get the following error:
forrtl: severe (157): Program Exception - access violation
The exact same code in Fortran 10 and Windows XP (64 bit) runs smoothly in Debug or Release modes.
Any idea why this is happening?
Thanks,
Pablo
0 Kudos
6 Replies
mecej4
Honored Contributor III
780 Views
It is quite likely that the error is caused by the portions of the code that you have not shown, or in the data file.

How is the array declared? What does the data file contain? Where is it located? In which line does the access violation occur? Which version of the compiler did you use?
0 Kudos
nvaneck
New Contributor I
780 Views
I've found the 64bit debugger to be probelmatical in other ways. It can't seem to associate the lines of code with break points for instance.I think I had crash problems, too, but it's been so long since I used it I can't remember. I haven't tried it since moving to release 12, so perhaps it's better now.

Since I generate release code for both 32bit and 64bit versions, I now always use the 32bit version for debugging.
0 Kudos
Pablo_Guerron
Beginner
780 Views
This are the declarations:

integer, parameter :: length_sample = 204
integer, parameter :: nofp = 15, nobs = 3, noftvp = 15
real (dp), dimension (nobs,length_sample) :: ourdata
The data are stored in a text file. The numbers are double precision.
Every time I set a breaking point at the "end do" line, the error happens.
Pablo
0 Kudos
Pablo_Guerron
Beginner
780 Views
Thanks for the suggestion.
0 Kudos
Steven_L_Intel1
Employee
780 Views
The debugger is not "crashing", it is your program that is getting an error. If you can attach a ZIP of your project, including everything needed to build and run the program, I'll be happy to take a look.
0 Kudos
Pablo_Guerron
Beginner
780 Views
It seems it is a problem with the 64 bit debugger and break points. The 32-bit does not return any error.
0 Kudos
Reply