On Apr 29, 2009, at 3:40 PM, Jed Brown wrote:
> But I'm able to replicate your error (but shouldn't the 2nd buffer
be
> the 1st + size (not 2)?) -- let me dig into it a bit... we
definitely
> shouldn't be getting invalid writes in the convertor, etc.
As Eugene pointed out earlier, it is fin
Jeff Squyres wrote:
> But I'm able to replicate your error (but shouldn't the 2nd buffer be
> the 1st + size (not 2)?) -- let me dig into it a bit... we definitely
> shouldn't be getting invalid writes in the convertor, etc.
As Eugene pointed out earlier, it is fine.
dataloctab = malloc (2 * (
On Apr 22, 2009, at 7:35 PM, François PELLEGRINI wrote:
I have had no answers regarding the trouble (OpenMPI bug ?)
I evidenced when combining OpenMPI and valgrind.
Sorry for the delay in getting back to you; there are so many mails
and only so many hours in the day... :-(
I tried it wi
Hello all,
I have had no answers regarding the trouble (OpenMPI bug ?)
I evidenced when combining OpenMPI and valgrind.
I tried it with a newer version of OpenMPI, and the problems
persist, with new, even more worrying, error messages being displayed :
==32142== Warning: client syscall munmap t
I'd like to add my concern to the thread at
http://www.open-mpi.org/community/lists/users/2009/03/8661.php that the
latest 1.3 series produces far too much memory-checker noise.
We use Valgrind extensively during debugging, and although I'm using the
latest snapshot (1.3.2a1r20901) and latest
Jeff Squyres wrote:
On Mar 28, 2009, at 5:31 AM, François PELLEGRINI wrote:
MPI_Comm_size (MPI_COMM_WORLD, &procglbnbr);
MPI_Comm_rank (MPI_COMM_WORLD, &proclocnum);
dataloctab = malloc (2 * (procglbnbr + 1) * sizeof (int));
dataglbtab = dataloctab + 2;
Why +2? Shouldn't it be +pr
On Mar 28, 2009, at 5:31 AM, François PELLEGRINI wrote:
MPI_Comm_size (MPI_COMM_WORLD, &procglbnbr);
MPI_Comm_rank (MPI_COMM_WORLD, &proclocnum);
dataloctab = malloc (2 * (procglbnbr + 1) * sizeof (int));
dataglbtab = dataloctab + 2;
Why +2? Shouldn't it be +procglbnbr?
3) Messag
Hello all,
When running a small MPI program under valgrind control,
I get worrying error messages :
==28358== Source and destination overlap in memcpy(0x4A726A0, 0x4A726A8, 16)
==28358==at 0x40236C9: memcpy (mc_replace_strmem.c:402)
==28358==by 0x407CA1C: ompi_ddt_copy_content_same_ddt (
