Hi,
I'm currently tracing a segfault in mpi_init which is caused
by ompi/runtime/ompi_mpi_init.c:569
ret = MCA_PML_CALL(add_procs(procs, nprocs));
free(procs);
In most cases, no segfault occurs and everything works fine,
but with some special combinations of machines, I can trigger
the b
Hi,
Adrian Knoth wrote:
> There are two issues found by valgrind, but I wanted to
> check the "normal" valgrind output first. With the nightly
> snapshot 1.2b1r12555, I got the following "errors":
>
> ==8948== Conditional jump or move depends on uninitialised value(s)
> ==8948==at 0x1B92884D:
Hi,
one of our projects recently exposed severe memory leakage when using
ROMIO to write a complex derived datatype (a struct made of other
structs) to a file. From our code we distilled the attached short
program to reproduce the leak.
After some Valgrind sessions, it appears as if the memcpy in
I'll fix the case in attr_create_predefined_callback - we should initialize
the rank variable first to be safe.
For your other question, do your configure with "--without-memory-manager".
Ralph
On 11/12/06 10:52 AM, "Adrian Knoth" wrote:
> Hi,
>
> I'm currently tracing a segfault in mpi_init
