Thanks - I expect we'll have to release 1.8.3 soon to fix this in case others
have similar issues. Out of curiosity, what OS are you using?
On Sep 1, 2014, at 9:00 AM, Matt Thompson wrote:
> Ralph,
>
> Okay that seems to have done it here (well, minus the usual
> shmem_mmap_enable_nfs_warnin
Ralph,
Okay that seems to have done it here (well, minus the
usual shmem_mmap_enable_nfs_warning that our system always generates):
(1033) $ setenv OMPI_MCA_shmem_mmap_enable_nfs_warning 0
(1034) $
/discover/nobackup/mathomp4/MPI/gcc_4.9.1-openmpi_1.8.2-debug-patch/bin/mpirun
-np 8 ./helloWorld.1
I never argue the standard with George, so I'll take his word for it.
I tried your program and it worked just fine for me without the sleep. However,
I still think there is something wrong in it. I tried adjusting the number of
processes and that caused it to hang, for one. Afraid I don't have
Based on the MPI standard (MPI 3.0 section 10.5.4 page 399) there is no
need to disconnect the child processes from the parent in order to cleanly
finalize. From this perspective, the original example is correct, but
sub-optimal as the parent processes calling MPI_Finalize might block until
all con
You need to disconnect the parent/child from each other prior to finalizing -
see the attached example
simple_spawn.c
Description: Binary data
On Aug 31, 2014, at 9:44 PM, Roy wrote:
> Hi all,
>
> I'm using MPI_Comm_spawn to start new child process.
> I found that if the parent process exe
Hi all,
I'm using MPI_Comm_spawn to start new child process.
I found that if the parent process execute MPI_Finalize before the child
process, the child process core dump on MPI_Finalize.
I couldn't find the correct way to have a clean shutdown of all processes
( parent and child ).
What that I f
