On Mon, 2009-06-08 at 23:41 -0600, tom fogal wrote: > George Bosilca <bosi...@eecs.utk.edu> writes: > > There is a whole page on valgrind web page about this topic. Please > > read http://valgrind.org/docs/manual/manual-core.html#manual-core.suppress > > for more information. > > Even better, Ralph (et al.) is if we could just make valgrind think > this is defined memory. One can do this with client requests: > > http://valgrind.org/docs/manual/mc-manual.html#mc-manual.clientreqs
Using the Valgrind client requests unnecessarily is a very bad idea, they are intended for where applications use their own memory allocator (i.e. replace malloc/free) or are using custom kernel modules or hardware which Valgrind doesn't know about. The correct solution is either to not send un-initialised memory or to suppress the error using a suppression file as George said. As the error is from MPI_Init() you can safely ignore it from a end-user perspective. Ashley. -- Ashley Pittman Padb - A parallel job viewer for cluster computing http://padb.pittman.org.uk
