Julian, Thanks for the info, and I'll check into OpenMPI 1.3 which I'm told has memcheck related developments in it.
The problems I'm having have nothing to do with MPI directly-- my test program has no MPI calls at all in it other than initialization and finalization, and I've tried writing to memory up to 512 bytes outside of the allocated memory block (both before and after), and get no error from valgrind. I suspect this suggestion is correct: > > 3. It may be that OpenMPI is providing its own implementations of > malloc, free, new, delete, etc; that Memcheck doesn't know about, > which will also cause chaos. > > > I suggest also that asking the OpenMPI developers is worthwhile. I've > found them in the past to be knowledgeable and helpful, and I believe they > are long-time users of Valgrind/Memcheck. > > I believe you should be able to get to essentially zero false errors > with a suitable OpenMPI configuration. I managed that in my testing with > OpenMPI a couple of years back, although I should say that was very > limited testing. I will contact them and see if they have any information. Thanks. -- Brian ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
