This is hardly an Open MPI issue:
switch the calls to MPI_Init, MPI_Finalize against
comment aut 'USE mpi' .... an see your error (SIGSEGV) again, now without any
MPI part in the program.
So my suspiction is this is an bug in your GCC version. Especially because there
is no SIGSEGV using 4.7.2 GCC (whereby it crasehs using 4.4.6)
==> Update your compilers!
On 01/11/13 14:01, Stefan Mauerberger wrote:
> Hi There!
> First of all, this is my first post here. In case I am doing something
> inappropriate pleas be soft with me. On top of that I am not quite sure
> whether that issue is related to Open MPI or GCC.
> Regarding my problem: Well, it is a little bulky, see below. I could
> figure out that the actual crash is caused by invoking Fortran's array
> constructor [ xx, yy ] on derived-data-types xx and yy. The one key
> factor is that those types have allocatable member variables.
> Well, that fact points to blame gfortran for that. However, the crash
> does not occur if MPI_Iinit is not called in before. Compiled as a
> serial program everything works perfectly fine. I am pretty sure, the
> lines I wrote are valid F2003 code.
> Here is a minimal working example:
> PROGRAM main
> USE mpi
> IMPLICIT NONE
> INTEGER :: ierr
> TYPE :: test_typ
> REAL, ALLOCATABLE :: a(:)
> END TYPE
> TYPE(test_typ) :: xx, yy
> TYPE(test_typ), ALLOCATABLE :: conc(:)
> CALL mpi_init( ierr )
> conc = [ xx, yy ]
> CALL mpi_finalize( ierr )
> END PROGRAM main
> Just compile with mpif90 ... and execute leads to:
>> *** glibc detected *** ./a.out: free(): invalid pointer: 0x00007fefd2a147f8 ***
>> ======= Backtrace: =========
> With commenting out 'CALL MPI_Init' and 'MPI_Finalize' everything seems to be fine.
> What do you think: Is this a OMPI or a GCC related bug?
> users mailing list
Dipl.-Inform. Paul Kapinos - High Performance Computing,
RWTH Aachen University, Center for Computing and Communication
Seffenter Weg 23, D 52074 Aachen (Germany)
Tel: +49 241/80-24915