There is not at this point. There's stuff in the works (HLRS is
working on some cool valgrind integration which goes beyond normal
memory checking), but it's not ready yet.
I'm aware of at least one place in the oob tcp that gets such a
warning (we're sending an entire struct down the wire, but there's
some "holes" in the memory such that we don't care about the values
and they are therefore uninitialized); where are you seeing the issue?
On Dec 17, 2007, at 4:08 PM, Lisandro Dalcin wrote:
> Dear all,
> I'm getting valgrind warnings related to syscalls with uninitialized
> memory (with release 1.2.4).
> Before providing more details and code reproducing the problem, I
> would like to know if there is any configure option I should take care
> of which enables extra memory initialization (--enable-debug is
> enough? I ask this because MPICH2 has specific configure option for
> this, perhaps you also have something similar).
> Lisandro Dalcín
> Centro Internacional de Métodos Computacionales en Ingeniería (CIMEC)
> Instituto de Desarrollo Tecnológico para la Industria Química (INTEC)
> Consejo Nacional de Investigaciones Científicas y Técnicas (CONICET)
> PTLC - Güemes 3450, (3000) Santa Fe, Argentina
> Tel/Fax: +54-(0)342-451.1594
> devel mailing list