~/Src/petsc/src/snes/examples/tutorials barry/fix-petsc $ grep joe ex1.c ~/Src/petsc/src/snes/examples/tutorials barry/fix-petsc $ echo $? 1
Well jeepers I just make grep “CRASH”. A nonzero return code denotes some condition, it doesn’t denote a crash. Barry On Feb 21, 2014, at 12:19 PM, Jeff Hammond <[email protected]> wrote: >>> Just configure MPICH such that snprintf isn't discovered by configure >>> and you won't see these messages. >>> >>> The other solution is to fix PETSc so that people can't crash it so easily >>> ;-) >> >> Here we go again. It is not CRASHING; it has detected an error >> conditioning and trying to appropriately and cleanly terminate. The reason >> it needs to use MPI_Abort() is that often detecting error conditions is not >> a uniformly collective thing. >> >> Printing a suitable error message and ending is not crashing. But with >> all the badly formatted “error messages” printed by MPICH I can not control >> at the end it looks like it is crashing. > > You're returning a non-zero exit code, which I consider crashing. I > apologize if this definition disagrees with yours. If this is just > gentle cleanup, why not exit with code=0 as Jim suggested already? > > Jeff > >>> On Thu, Feb 20, 2014 at 3:19 PM, Jim Dinan <[email protected]> wrote: >>>> If you can find a way to call MPI_Finalize instead, you will portably >>>> eliminate these messages. >>>> >>>> A lesser solution would be to provide an error code of 0 (or MPI_SUCCESS) >>>> to >>>> MPI_Abort, e.g. MPI_Comm_abort(MPI_COMM_WORLD, MPI_SUCCESS). This would >>>> eliminate the error message that you are getting from the job launcher. >>>> MPICH could be modified to be quiet about the abort when the application >>>> aborts with an error code of MPI_SUCCESS. >>>> >>>> ~Jim. >>>> >>>> >>>> On Thu, Feb 20, 2014 at 12:33 PM, Barry Smith <[email protected]> wrote: >>>>> >>>>> >>>>> Is there any way to turn off MPICH (and others) printing messages about >>>>> MPI_Abort? We have already prepared and presented useful error messages >>>>> to >>>>> the user about the situation and would like to avoid having these >>>>> additional >>>>> messages printed (that often make the situation look worse than it is) >>>>> >>>>> Thanks >>>>> >>>>> Barry >>>>> >>>>> application called MPI_Abort(MPI_COMM_WORLD, 56) - process 0 >>>>> [cli_0]: aborting job: >>>>> application called MPI_Abort(MPI_COMM_WORLD, 56) - process 0 >>>>> >>>>> >>>>> ==================================================================mailto:[email protected]================= >>>>> = BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES >>>>> = EXIT CODE: 56 >>>>> = CLEANING UP REMAINING PROCESSES >>>>> = YOU CAN IGNORE THE BELOW CLEANUP MESSAGES >>>>> >>>>> =================================================================================== >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> discuss mailing list [email protected] >>>>> To manage subscription options or unsubscribe: >>>>> https://lists.mpich.org/mailman/listinfo/discuss >>>> >>>> >>>> >>>> _______________________________________________ >>>> discuss mailing list [email protected] >>>> To manage subscription options or unsubscribe: >>>> https://lists.mpich.org/mailman/listinfo/discuss >>> >>> >>> >>> -- >>> Jeff Hammond >>> [email protected] >>> _______________________________________________ >>> discuss mailing list [email protected] >>> To manage subscription options or unsubscribe: >>> https://lists.mpich.org/mailman/listinfo/discuss >> >> _______________________________________________ >> discuss mailing list [email protected] >> To manage subscription options or unsubscribe: >> https://lists.mpich.org/mailman/listinfo/discuss > > > > -- > Jeff Hammond > [email protected] > _______________________________________________ > discuss mailing list [email protected] > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss
