Hi Dave, The memchecker interface is an addition which allows other tools to be used as well.
A more recent one is memPin [1]. As stated in the cited paper, the overhead is minimal when not attached to a tool. >From my experience a program running under pin tool control runs much faster >than valgrind. Best Christoph Niethammer [1] http://www.springer.com/cda/content/document/cda_downloaddocument/9783642373480-c1.pdf?SGWID=0-0-45-1397615-p175067491 ----- Original Message ----- From: "Dave Love" <dave.l...@manchester.ac.uk> To: "Open MPI Users" <users@lists.open-mpi.org> Sent: Thursday, August 24, 2017 1:22:17 PM Subject: [OMPI users] built-in memchecker support Apropos configuration parameters for packaging: Is there a significant benefit to configuring built-in memchecker support, rather than using the valgrind preload library? I doubt being able to use another PMPI tool directly at the same time counts. Also, are there measurements of the performance impact of configuring, but not using, it with recent hardware and software? I don't know how relevant the results in https://www.open-mpi.org/papers/parco-2007/ would be now, especially on a low-latency network. _______________________________________________ users mailing list users@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/users _______________________________________________ users mailing list users@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/users
