On 02/04/2013 05:26 PM, Raghu Reddy wrote: > r4i0n0% mpicc -DBUG -g -O0 -o hello_mpi_c hello_mpi_c.c > /contrib/valgrind/valgrind-3.8.1/lib/valgrind/libmpiwrap-amd64-linux.so > r4i0n0% > r4i0n0% env MPIWRAP_DEBUG=verbose mpiexec_mpt -np 1 > /contrib/valgrind/valgrind-3.8.1/bin/valgrind -v ./hello_mpi_c > valgrind MPI wrappers 9681: Active for pid 9681 > valgrind MPI wrappers 9681: Try MPIWRAP_DEBUG=help for possible options > valgrind MPI wrappers 9681: enter PMPI_Init > valgrind MPI wrappers 9681: enter PMPI_Init_thread > valgrind MPI wrappers 9681: exit PMPI_Init (err = 0) > valgrind MPI wrappers 9681: enter PMPI_Comm_rank > valgrind MPI wrappers 9681: exit PMPI_Comm_rank (err = 0) > valgrind MPI wrappers 9681: enter PMPI_Comm_size > valgrind MPI wrappers 9681: exit PMPI_Comm_size (err = 0) > valgrind MPI wrappers 9681: enter PMPI_Get_processor_name > Hello from rank 0 out of 1; procname = r4i0n0 > Print something 0 > valgrind MPI wrappers 9681: enter PMPI_Finalize > valgrind MPI wrappers 9681: exit PMPI_Finalize (err = 0)
It looks as if Valgrind didn't run at all in this case, that is, hello_mpi_c is executed natively. This might be something to do with mpiexec -- we've had strange interactions with such programs (normally called mpirun) before now. Can you get any logging information out of mpiexec, to get some insight into what is going on? J ------------------------------------------------------------------------------ Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
