On Mon, 2012-05-07 at 21:15 +0200, Martin Kalany wrote:
> Nevertheless, valgrind doesn't print anything similar to
> "valgrind MPI wrappers 31901: Active for pid 31901
> valgrind MPI wrappers 31901: Try MPIWRAP_DEBUG=help for possible options"
> as stated in the documentation. How do I know whether or not the mpi
> wrappers now work?
If you add the option --trace-redir=yes to your Valgrind args,
Valgrind will trace all the actions related to redirection/wrapping:
* it will trace the creation of the redir specifications
(e.g; when loading the libmpiwrap which is part of Valgrind)
* it will trace the resulting "active" redirections or wrappings.
For what concerns the original problem: I understand it is because
Valgrind was configured with a different mpi that the one you are using
and that created a mixup in the libs. Is that the explanation ?
Philippe
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
