Am 07.05.2012 21:34, schrieb Dave Goodell: > On May 7, 2012, at 2:15 PM CDT, Martin Kalany wrote: > >> Am 06.05.2012 00:54, schrieb Philippe Waroquiers: >>> On Sun, 2012-05-06 at 00:24 +0200, Martin Kalany wrote: >>>>> Valgrind documation states that "The MPI functions to be wrapped are >>>>> assumed to be in an ELF shared object with soname matching libmpi.so*. >>>>> This is known>to be correct at least for Open MPI and Quadrics MPI, and >>>>> can easily be changed if required." >>> Note that the documentation is slightly out of date, as the code >>> contains the pattern libmpi*.so* >>> (so as to match a.o. libmpich.so.1.0). >>> >>> Philippe >> Thanks a lot for your help Phillippe! You finally led me in the right >> direction: >> I found a workaround for the problem: I simply renamed libmpich.so to >> libmpi.so and the error was gone. > That sounds like it will cause other problems. Do your applications still > run correctly after the rename? To be more precise: I did a copy+rename, so the original still exists. > >> 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? > I'm guessing that they aren't working. I've hit this (not the "libmpi.so" > name issue) in the past when linking statically instead of dynamically. > > How are you compiling and linking your code? With "mpicc"? Yes, I'm using mpicc to compile and link. > > What does "ldd YOUR_BINARY_HERE" give you? You should see lines that look > like this in the output: > > ----8<---- > libmpich.so.6 => > /sandbox/goodell/mpich2-installed/lib/libmpich.so.6 (0x00007fb786ffa000) > libopa.so.1 => /sandbox/goodell/mpich2-installed/lib/libopa.so.1 > (0x00007fb786df8000) > libmpl.so.1 => /sandbox/goodell/mpich2-installed/lib/libmpl.so.1 > (0x00007fb786bf1000) > ----8<---- > > -Dave > > ldd gives me libmpi.so.0, but no mpich-related .so files
And I guess that's the problem, right? I already reinstalled vlagrind using ./configure --with-mpicc=path/to/mpich/ (as you suggested on stackoverflow. That question there is from me, if you haven't noticed yet). Thanks for your help! Martin ------------------------------------------------------------------------------ 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 [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
