>> This might be a good place to start? It describes the >> MPI_Errhandler_create and MPI_Errhandler_set interfaces. > > Thanks, but according to this, MPI's default behavior should already > be what I want: to do an MPI_Abort on any errors. > > Of course, even when I do an MPI_Abort(COMM_WORLD, myerrorcode) > manually, "myerrorcode" only gets printed to the screen, and the code > "1" gets returned to the OS instead. So perhaps my problem isn't with > the MPI spec but with the particular MPICH 1.2.7 implementation...
For what it's worth, I've found both MPICH2 and OpenMPI to be much better in terms of properly killing tasks and generally handling aborts better. Of course, they are both MPI-2 implementations, and in general I don't want to require MPI2 for library support, but it may be worth using it during development nonetheless. -Ben ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Libmesh-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
