Joseph,
the goal is to plug all the memory leaks (e.g. not simply filter them)
there is an ongoing effort at https://github.com/open-mpi/ompi/pull/2175
but i must admit this is not a high priority one (and it will take a bit
more time before all the fixes land
into the stable branches
Che
Gilles,
Thanks a lot for the fix. I just tested on master and can confirm that
both the leak and the invalid read-writes are gone. However, the
suppression file still does not filter the memory that is allocated in
MPI_Init and not properly free'd at the end. Any chance this can be
filtered u
Joseph,
thanks for the report, this is a real memory leak.
i fixed it in master, and the fix is now being reviewed.
meanwhile, you can manually apply the patch available at
https://github.com/open-mpi/ompi/pull/2418.patch
Cheers,
Gilles
On Tue, Nov 15, 2016 at 1:52 AM, Joseph Schuchart wrote:
Hi Luke,
Thanks for your reply. From my understanding, the wrappers mainly help
catch errors on the MPI API level. The errors I reported are well below
the API layer (please correct me if I'm wrong here) However, I re-ran
the code with the wrapper loaded via LD_PRELOAD and without the
suppres
Hi Joesph,
I don’t have a solution to your issue, but I’ve found that the valgrind mpi
wrapper is necessary to eliminate many of the false positives that the
suppressions file can’t.
http://valgrind.org/docs/manual/mc-manual.html#mc-manual.mpiwrap.gettingstarted
You should LD_PRELOAD the libmp
All,
I am investigating an MPI application using Valgrind and see a load of
memory leaks reported in MPI-related code. Please find the full log
attached. Some observations/questions:
1) According to the information available at
https://www.open-mpi.org/faq/?category=debugging#valgrind_clean
