"Segmentation Fault (Core Dumped)" Error in Fortran Gfortran Linux

Segmentation Fault (core dumped) error in Fortran gfortran linux

The most frequent causes of fatal memory errors in Fortran are illegal array subscripts and inconsistency between the arguments of the call to a procedure (subroutine or function) and what the declared arguments of the procedure. For the first, turn on run-time subscript checking. With gfortran, -fcheck=bounds, or better, turn on additional run-time checks with -fcheck=all. For the procedure argument issue, place all of your procedures into module(s) and use those module(s) from any routine that calls any of the procedures. This will enable the compiler to check argument consistency at compile time.

Fortran strange segmentation fault

The problem comes from the size of the stack used by some compilers by default (ifort) or by some others when they optimise the compilation (gfortran -Ofast). Here, our writings exceed the size of the stack.

To solve this, I use the options -heap-arrays for ifort compiler and -fno-stack-arrays for gfortran compiler.

Why does this 3-line gfortran code throw a segmentation fault?

So, very unfortunately, GFortran v5.1.0 is bugged such that valid files will cause a segfault when OPENed. Try updating to v5.2 or higher.

Segmentation fault - invalid memory reference

As far as I can tell, there could be a number of problems:

• Your integers with INTEGER*8 might be too long, maybe INTEGER*4 or simply INTEGER would be better
• You call SGESV on double arguments instead of DGESV
• Your LDA argument is missing, so your code should perhaps look like CALL DGESV(N,N,DMA2,N,pivot,FU,N,inf) but you need to check whether this is what you want.

FORTRAN Segmentation Fault

Perhaps you need to increase the stack size on those machines. There are answers on this subject on Stackoverflow. Check ulimit.

---

Related Topics