Subject: Re: [OMPI users] Valgrind writev() errors with 1.3.2.
From: Jeff Squyres (jsquyres_at_[hidden])
Date: 2009-06-09 09:28:02
This is worth adding to the FAQ.
On Jun 9, 2009, at 2:31 AM, Ashley Pittman wrote:
> On Mon, 2009-06-08 at 23:41 -0600, tom fogal wrote:
> > George Bosilca <bosilca_at_[hidden]> 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
>
> _______________________________________________
> users mailing list
> users_at_[hidden]
> http://www.open-mpi.org/mailman/listinfo.cgi/users
>
-- Jeff Squyres Cisco Systems