just to add to previous replies seg faults are usually caused when adressing a location outside array bounds (many times you try to reach the 0 element)
also if you compile your code using the debug flag -g it will tell you where the fault occures.
Hello
i am runing an ecological model in fortran which calls a single subroutine from about 200 different places in a source code divided to about 50 text files. after ca. 2 days of running i have a devision by zero and the model blows up - this is a tough thing to debug. if i use debug flag...
just for the record i used formatted text files as suggested below:
Unformatted files are non-portable, especially between machines with different word sizes and floating-point representations. There may be utilities available to help with the conversion. Simply writing an unformatted file on...
I am trying to deploy my oceanic model currently runing on ubuntu linux and compiled with intel fortran on a cray sv1 machine with UNICOS operating system.
It actually went quite well until i tried to read unformatted files. i am using the following code to export the data to the new machine...
i have a fortran 90 function invoked:
iret = store_data(ncid_bfm,var_ids(n),OCET_SHAPE,NO_BOXES,garray=D3DIAGNOS(i,:))
each time i get to that line i get segmentation fault
[SIZE="3"]
on the calling unit variables a defined like so:
!BOP
!
! !IROUTINE: Store the results
!
...