On May 7, 2012, at 3:54 PM CDT, Philippe Waroquiers wrote: > 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 ?
I don't think this has been confirmed, but something along these lines seems like the most likely explanation to me. I just tried the Valgrind 3.7.0 MPI wrapper with MPICH2 on Linux and it worked just fine without any library renaming. -Dave ------------------------------------------------------------------------------ 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
