We have made more of an effort to get valgrind clean on the master - haven’t
brought all of it across due to the desire to minimize change in 1.8
I’ll see what can be done, probably more for 1.8.5 at this point. Most of these
look like legitimate leaks that should be addressed as opposed to suppressed.
> On Dec 12, 2014, at 8:00 AM, Eric Chamberland
> <eric.chamberl...@giref.ulaval.ca> wrote:
>
> 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.c
>
> mpiexec -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>_______________________________________________
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post:
> http://www.open-mpi.org/community/lists/devel/2014/12/16545.php
