[mpich2-dev] Parent terminates when the spawned child terminates

Lisandro Dalcin dalcinl at gmail.com
Wed Dec 15 10:27:09 CST 2010


On 15 December 2010 13:18, Suraj Prabhakaran
<suraj.prabhakaran at gmail.com> wrote:
> Hello,
>
> By default, when a spawned child terminates (through exit() or mpi_abort()
> and *NOT* throught MPI_finalize() ), the parent also terminates with a
> message
>
> APPLICATION TERMINATED WITH THE EXIT STRING: Hangup (signal 1)
>
> I am not sure what exactly the standard specifies for such a situation but
> it kind of defeats the purpose of parent-child relationship.
>

I think the standard is pretty clear about this:
http://www.mpi-forum.org/docs/mpi22-report/node226.htm#Node226

>I would be glad
> to know if there is any specific reason why it is implemented this way and
> why it should stay this way. If there is no specific reason, may I request
> that a work around for this is implemented?
>

Did you try to use register an atexit() callback [and a SIGABRT
handler for the case of abort()]?




-- 
Lisandro Dalcin
---------------
CIMEC (INTEC/CONICET-UNL)
Predio CONICET-Santa Fe
Colectora RN 168 Km 472, Paraje El Pozo
Tel: +54-342-4511594 (ext 1011)
Tel/Fax: +54-342-4511169


More information about the mpich2-dev mailing list