This web mail archive is frozen.
This page is part of a frozen web archive of this mailing list.
You can still navigate around this archive, but know that no new mails
have been added to it since July of 2016.
Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.
On 2014/05/28 12:10, Ralph Castain wrote:
> my understanding is that there are two ways of seeing things :
> a) the "R-way" : the problem is the parent should not try to communicate to already exited processes
> b) the "J-way" : the problem is the children should have waited either in MPI_Comm_free() or MPI_Finalize()
> I don't think you can use option (b) - we can't have the children lingering around for the parent to call finalize, if I'm understanding you correctly.
you understood me correctly.
once again, i did not start investigating loop_spawn.
in the case of intercomm_create, we would not run into this if the
application had explicitly called MPI_Comm_free in the parent.
so in this case *only*, and as explained by Jeff, b) could be an option
to make OpenMPI happy.
(to be blunt : if the user is not happy with children lingering around,
he can explicitly call MPI_Comm_free before calling MPI_Comm_disconnect)
i will start investigating loop_spawn from now