On 12/11/2014 05:45 AM, Ralph Castain wrote: ...
by the reporters. Still, I would appreciate a fairly thorough testing as this is expected to be the last 1.8 series release for some time.
Is is relevant to report valgrind leaks? Maybe they are "normal" or not, I don't know. If they are normal, maybe suppressions should be added to .../share/openmpi/openmpi-valgrind.supp before the release?
Here is a simple test case ;-) : cat mpi_init_finalize.c #include "mpi.h" int main(int argc, char *argv[]) { MPI_Init(&argc, &argv); MPI_Finalize(); return 0; } mpicc -o mpi_init_finalize mpi_init_finalize.cmpiexec -np 1 valgrind -v --suppressions=/opt/openmpi-1.8.4rc2/share/openmpi/openmpi-valgrind.supp --gen-suppressions=all --leak-check=full --leak-resolution=high --show-reachable=yes --error-limit=no --num-callers=24 --track-fds=yes --log-file=valgrind_out.n%q{OMPI_COMM_WORLD_RANK} ./mpi_init_finalize
running with 2 processes generates some more:mpiexec -np 2 .... --log-file=valgrind_out_2proc.n%q{OMPI_COMM_WORLD_RANK} ./mpi_init_finalize
which results in the files attached... Thanks, Eric
valgrind_out.tgz
Description: application/compressed-tar