bemery@nmsu.edu (Bryan Emery) (10/26/90)
I have a program that is about 3000 lines long. It compiles and runs under VMS 5.0 Fortran with no problems. It also compiled and ran on a SUN 4. However, on my DECstation 3100 (supposed to be much faster than my VAX) it compiles with some WARNINGS - no ERRORS. When I try to execute the result it runs for a short time (about 3-5 minutes) then does a core dump and quits with no explicit error message. I tried using the debugger but I don't know much about using debugger. Any suggestions?? Bryan Emery
frank@croton.enet.dec.com (Frank Wortner) (10/26/90)
Try compiling with the -C ("check array bounds") option and
then rerunning the program. In fact, try compiling on VMS
with the /CHECK option or on the Sun with whatever their
corresponding option is. It is amazing how many FORTRAN
programs attempt to store information in the 150th element
of a 100 element array. ;-)
Frankthewalt@canuck.ce.berkeley.edu (C. Thewalt) (10/26/90)
In article <244@opus.NMSU.Edu> bemery@nmsu.edu (Bryan Emery) writes:
I have a program that is about 3000 lines long. It compiles and runs under
VMS 5.0 Fortran with no problems. It also compiled and ran on a SUN 4.
However, on my DECstation 3100 (supposed to be much faster than my VAX)
it compiles with some WARNINGS - no ERRORS. When I try to execute the
result it runs for a short time (about 3-5 minutes) then does a core dump
and quits with no explicit error message. I tried using the debugger but
I don't know much about using debugger.
Any suggestions??
Bryan Emery
Although DEC and I don't see eye to eye on whether this is a bug, try
compiling with the -static flag and see if it works better. From what
I can tell this flag is mandatory to get semi-normal behavior out of
the fortran compiler.
I claim this is a bug, because it is necessary even on small programs
with no subroutines, when by the description in the man page it sounds
like it is necessary only for those who are taking liberties with
local variable in subroutines.
Anyway, worth a try...
Chris
--
Christopher Robin Thewalt These opinions are not necessarily
thewalt@ce.berkeley.edu shared by my employer...
University of California, Berkeley