Ah, wait -- based on your mail, I checked the MPI_Info-checking code in our
underlying spawn implementation and basically found an uninitialized variable.
Hence, it's probably non-deterministic behavior.
Patch coming to the development trunk soon; I'll get it QA checked by someone
more expert i
Thanks for that info!
I was literally just digging into this myself; I am able to replicate the
problem on a 1.5.1 tarball, but not on a nightly 1.5.2 snapshot tarball. Would
you mind trying to replicate the issue on a recent 1.5.2 snapshot?
http://www.open-mpi.org/nightly/v1.5/
On Jan 2
Hello,
I figured out the problem, which is described herein, it might be
useful for someone else. The problem stems from ompi_local_slave option
being set on its own in the MPI_Info structure. It seems that
MPI_Info_create is using a shift or more likely a masking operation
(depending upon th
Hello,
I have compiled openmpi-1.5.1 as a 32-bit binary on a 64-bit
architecture. I have a problem using MPI_Comm_spawn and
MPI_Comm_spawn_multiple, when MPI_Info is used as a non NULL
(MPI_INFO_NULL) parameter. I get a segmentation fault. I have
the exact
