Which version of MPICH were you running?

-- 
Hui Zhou

From: "Mccall, Kurt E. (MSFC-EV41) via discuss" <discuss@mpich.org>
Reply-To: "discuss@mpich.org" <discuss@mpich.org>
Date: Monday, April 6, 2020 at 12:45 PM
To: "discuss@mpich.org" <discuss@mpich.org>
Cc: "Mccall, Kurt E. (MSFC-EV41)" <kurt.e.mccall@nasa.gov>
Subject: Re: [mpich-discuss] Abnormal termination on Linux

I should mention that I am unable to predict in which node or process the abnormal termination occurs, so I can’t practically attach a debugger and try to intercept the error.

Kurt

From: Mccall, Kurt E. (MSFC-EV41) <kurt.e.mccall@nasa.gov>
Sent: Monday, April 6, 2020 11:50 AM
To: discuss@mpich.org
Cc: Mccall, Kurt E. (MSFC-EV41) <kurt.e.mccall@nasa.gov>
Subject: Abnormal termination on Linux

I have a couple of questions about abnormal termination.   The EXIT CODE below is 11, which could be signal SIGSEGV, or is it something defined by MPICH?  If it is SIGSEGV, it is strange because my signal handler isn’t catching it and cleaning up properly (the signal handler calls MPI_Finalize()).   Is there any way to get more information about the location of the error?

=   BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES

=   PID 14385 RUNNING AT n020.cluster.com

=   EXIT CODE: 11

=   CLEANING UP REMAINING PROCESSES

=   YOU CAN IGNORE THE BELOW CLEANUP MESSAGES

Thanks,

Kurt