[MPICH2-dev] possible bug in mpich2

Rajeev Thakur thakur at mcs.anl.gov
Tue May 16 21:02:50 CDT 2006


Well, you are not using much of MPI in this code other than init, finalize,
comm_rank, comm_size. If you comment out everything else in the code other
than these MPI functions, and the code runs, you can eliminate the
possibility that the problem may be in MPI.

Rajeev 


> -----Original Message-----
> From: owner-mpich2-dev at mcs.anl.gov 
> [mailto:owner-mpich2-dev at mcs.anl.gov] On Behalf Of Kamaraju Kusumanchi
> Sent: Sunday, May 14, 2006 1:55 AM
> To: mpich2-dev at mcs.anl.gov
> Subject: [MPICH2-dev] possible bug in mpich2
> 
> A sample test code (test.f90) is attached in this mail.
> 
> I think this is a valid fortran 90 code. The program compiles fine.
> But I am unable to execute it. I dont know whether it is a gfortran
> bug or mpich2 bug. Sorry if this is the wrong forum. Please direct me
> as to where I should report this problem.
> 
> To reproduce the problem
> 
> $make
> mpif90   -c test.f90 -o test.o
> 
> mpif90  test.o    -o test
> 
> $mpiexec -l -n 4 ./test
> rank 0 in job 5  kusumanchi_56156   caused collective abort 
> of all ranks
>   exit status of rank 0: killed by signal 11
> 
> 
> I am using Debian unstable.
> 
> 
> $gfortran -v
> Using built-in specs.
> Target: i486-linux-gnu
> Configured with: ../src/configure -v
> --enable-languages=c,c++,java,f95,objc,ada,treelang --prefix=/usr
> --enable-shared --with-system-zlib --libexecdir=/usr/lib
> --without-included-gettext --enable-threads=posix --enable-nls
> --program-suffix=-4.0 --enable-__cxa_atexit --enable-clocale=gnu
> --enable-libstdcxx-debug --enable-java-awt=gtk-default
> --enable-gtk-cairo
> --with-java-home=/usr/lib/jvm/java-1.4.2-gcj-4.0-1.4.2.0/jre
> --enable-mpfr --disable-werror --with-tune=i686
> --enable-checking=release i486-linux-gnu
> Thread model: posix
> gcc version 4.0.4 20060507 (prerelease) (Debian 4.0.3-3)
> 
> 
> $mpif90 -v
> mpif90 for 1.0.3
> Driving: gfortran -g -O2 -v
> -I/home/software/compiledLibs/mpich2_1.0.3_gcc_4.0.3_gfortran_
> 4.0.3/include
> -I/home/software/compiledLibs/mpich2_1.0.3_gcc_4.0.3_gfortran_
> 4.0.3/include
> -L/home/software/compiledLibs/mpich2_1.0.3_gcc_4.0.3_gfortran_
> 4.0.3/lib
> -lmpichf90 -lmpichf90 -lmpich -lpthread -lrt -lgfortranbegin
> -lgfortran -lm -shared-libgcc
> Using built-in specs.
> Target: i486-linux-gnu
> Configured with: ../src/configure -v
> --enable-languages=c,c++,java,f95,objc,ada,treelang --prefix=/usr
> --enable-shared --with-system-zlib --libexecdir=/usr/lib
> --without-included-gettext --enable-threads=posix --enable-nls
> --program-suffix=-4.0 --enable-__cxa_atexit --enable-clocale=gnu
> --enable-libstdcxx-debug --enable-java-awt=gtk-default
> --enable-gtk-cairo
> --with-java-home=/usr/lib/jvm/java-1.4.2-gcj-4.0-1.4.2.0/jre
> --enable-mpfr --disable-werror --with-tune=i686
> --enable-checking=release i486-linux-gnu
> Thread model: posix
> gcc version 4.0.4 20060507 (prerelease) (Debian 4.0.3-3)
>  /usr/lib/gcc/i486-linux-gnu/4.0.4/collect2 --eh-frame-hdr -m elf_i386
> -dynamic-linker /lib/ld-linux.so.2
> /usr/lib/gcc/i486-linux-gnu/4.0.4/../../../../lib/crt1.o
> /usr/lib/gcc/i486-linux-gnu/4.0.4/../../../../lib/crti.o
> /usr/lib/gcc/i486-linux-gnu/4.0.4/crtbegin.o
> -L/home/software/compiledLibs/mpich2_1.0.3_gcc_4.0.3_gfortran_
> 4.0.3/lib
> -L/usr/lib/gcc/i486-linux-gnu/4.0.4
> -L/usr/lib/gcc/i486-linux-gnu/4.0.4
> -L/usr/lib/gcc/i486-linux-gnu/4.0.4/../../../../lib
> -L/usr/lib/gcc/i486-linux-gnu/4.0.4/../../.. -L/lib/../lib
> -L/usr/lib/../lib -lmpichf90 -lmpichf90 -lmpich -lpthread -lrt
> -lgfortranbegin -lgfortran -lm -lgcc_s -lgcc -lc -lgcc_s -lgcc
> /usr/lib/gcc/i486-linux-gnu/4.0.4/crtend.o
> /usr/lib/gcc/i486-linux-gnu/4.0.4/../../../../lib/crtn.o
> /usr/lib/gcc/i486-linux-gnu/4.0.4/../../../../lib/libgfortranb
egin.a(fmain.o):
> In function `main': undefined reference to `MAIN__'
> collect2: ld returned 1 exit status
> 
> While compiling mpich2, I used gcc 4.0.3, gfortran 4.0.3. Currently my
> machine is running 4.0.4 . Dont know if the version difference
> matters. But I wanted to inform you in case it does matter.
> 
> thanks
> raju
> 




More information about the mpich2-dev mailing list