Subject: Re: [OMPI users] Valgrind writev() errors with 1.3.2.
From: Åke Sandgren (ake.sandgren_at_[hidden])
Date: 2009-06-09 14:12:25
On Tue, 2009-06-09 at 12:01 -0600, Ralph Castain wrote:
> I can't speak to all of the OMPI code, but I can certainly create a
> new configure option --valgrind-friendly that would initialize the OOB
> comm buffers and other RTE-related memory to eliminate such warnings.
>
> I would prefer to configure it out rather than adding a bunch of
> "if-then" checks for envars to avoid having the performance hit when
> not needed.
> Would that help?
Yes please!!!
I gave up the last attempt at finding memory problems in a user code
simply because the amount of complaints from the openmpi parts.
-- Ake Sandgren, HPC2N, Umea University, S-90187 Umea, Sweden Internet: ake_at_[hidden] Phone: +46 90 7866134 Fax: +46 90 7866126 Mobile: +46 70 7716134 WWW: http://www.hpc2n.umu.se