corrupt object module when compiling huge program with debug

sorry for the confusion I meant I used the command line ftn95 *.f90 My code is still in 77 format rather than f90, so that's my default

Of course I had to rename the file in your post and I used the actual name I had given it and not *.f90

And what was that actual name? That is rather important, considering what has been discussed earlier in this thread regarding reserved device names.

I called it test1.f90 so the command line calls were ftn95 test1.f90 /link or ftn95 test1.f90 /link/debug

I trust this is unambiguous. Louis

I renamed the file to 'test1.f90' and tried the four combinations of /64 and /debug. In every case the compiler crashed with an attempt to read from location 00000000.

At this point it would be useful if other forum readers could try the same tests and tell us what they find.

I compiled mecej4's example in Plato I had gFortran selected for /64 and the response in errorlog was:

test_com.f90:5:15: 5 | end module com3 | 1 Fatal Error: Cannot open module file 'com3.mod0' for writing at (1): No such file or directory

compilation terminated.

FTN95 needs to trap this possible error

FTN95 has now been fixed for the next release so that the failure to create the file COM3.mod will generate an error report.

If there are other outstanding issues in this thread the please let me know,