[petsc-dev] Should PetscSignalHandlerDefault avoid calling MPI_Abort?

[John Peterson]

Hi,

I started a thread on discuss at mpich.org regarding some hanging canceled
jobs that we were seeing:

https://lists.mpich.org/pipermail/discuss/2020-April/005910.html

It turns out that there are some fairly strict rules about what types of
functions (asynchronous-safe only) can be called from signal handlers, and
MPI_Abort(), at least the mpich implementation of it, apparently does not
fall into that category. I wonder if you have any comments on this. One
possibility might be might be to just call "_exit" from
PetscSignalHandlerDefault rather than PETSCABORT, not sure what other
issues that would cause, however.

Thanks,
John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20200421/bced7f34/attachment.html>