Hello,

Could you please report this bug to mpich2 upstream?

https://trac.mcs.anl.gov/projects/mpich2

You'll need to register and login before filing the ticket.

  -- Pavan

On 09/03/2012 08:22 AM, Evren Yurtesen wrote:
> Public bug reported:
>
> I am compiling a test program on 12.04 with latest updates:
> http://people.sc.fsu.edu/~jburkardt/f_src/mpi_stubs/hello.f90
>
> It works fine normally:
> $ ./a.out
>
> HELLO_WORLD - Master process:
>    FORTRAN90 version
>    An MPI test program.
>
>    The number of processes is   1
>
>    Process   0 says "Hello, world!"
>
> HELLO_WORLD:
>    Normal end of execution.
> eyurtese@supremum:~$ mpirun -n 2 ./a.out
>
> HELLO_WORLD - Master process:
>    FORTRAN90 version
>    An MPI test program.
>
>    The number of processes is   2
>
>    Process   0 says "Hello, world!"
>    Process   1 says "Hello, world!"
>
> HELLO_WORLD:
>    Normal end of execution.
>
> If I run it with valgrind:
> $ mpirun -n 2 valgrind ./a.out
> ==26486== Memcheck, a memory error detector
> ==26486== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
> ==26486== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
> ==26486== Command: ./a.out
> ==26486==
> ==26487== Memcheck, a memory error detector
> ==26487== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
> ==26487== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
> ==26487== Command: ./a.out
> ==26487==
> ==26486== Warning: ignored attempt to set SIGRT32 handler in sigaction();
> ==26486==          the SIGRT32 signal is used internally by Valgrind
> ==26487== Warning: ignored attempt to set SIGRT32 handler in sigaction();
> ==26487==          the SIGRT32 signal is used internally by Valgrind
> cr_libinit.c:183 cri_init: sigaction() failed: Invalid argument
> cr_libinit.c:183 cri_init: sigaction() failed: Invalid argument
> ==26486==
> ==26486== HEAP SUMMARY:
> ==26486==     in use at exit: 0 bytes in 0 blocks
> ==26486==   total heap usage: 5 allocs, 5 frees, 8,165 bytes allocated
> ==26486==
> ==26486== All heap blocks were freed -- no leaks are possible
> ==26486==
> ==26486== For counts of detected and suppressed errors, rerun with: -v
> ==26486== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 2 from 2)
> ==26487==
> ==26487== HEAP SUMMARY:
> ==26487==     in use at exit: 0 bytes in 0 blocks
> ==26487==   total heap usage: 5 allocs, 5 frees, 8,165 bytes allocated
> ==26487==
> ==26487== All heap blocks were freed -- no leaks are possible
> ==26487==
> ==26487== For counts of detected and suppressed errors, rerun with: -v
> ==26487== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 2 from 2)
>
> =====================================================================================
> =   BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES
> =   EXIT CODE: 134
> =   CLEANING UP REMAINING PROCESSES
> =   YOU CAN IGNORE THE BELOW CLEANUP MESSAGES
> =====================================================================================
> APPLICATION TERMINATED WITH THE EXIT STRING: Aborted (signal 6)
>
>
> I have manually compiled Valgrind 3.8 and I am getting the same error, which makes me think that the problem is mpich2.
>
> Also I found a thread which mentions that somebody had same problem fixed by upgrading mpich2 from 1.3 to 1.4 but we already have 1.4.1 in ubuntu, so perhaps an update to 1.4.1p1 would be good?  (I think it has nothing to do with the versions but perhaps compiling against newer libraries does help).
> http://lists.mcs.anl.gov/pipermail/mpich-discuss/2011-August/010608.html
>
> if the problem is libcr, then somebody must put a note to recompile
> mpich2 package everytime libcr is updated.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 12.04
> Package: mpich2 1.4.1-1ubuntu1
> ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
> Uname: Linux 3.2.0-29-generic x86_64
> NonfreeKernelModules: fglrx
> ApportVersion: 2.0.1-0ubuntu12
> Architecture: amd64
> Date: Mon Sep  3 16:14:10 2012
> InstallationMedia: This
> ProcEnviron:
>   TERM=xterm
>   PATH=(custom, no user)
>   LANG=en_US.UTF-8
>   SHELL=/bin/bash
> SourcePackage: mpich2
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> ** Affects: mpich2 (Ubuntu)
>       Importance: Undecided
>           Status: New
>
>
> ** Tags: amd64 apport-bug precise running-unity
>

-- 
Pavan Balaji
http://www.mcs.anl.gov/~balaji