<div dir="ltr">A little more detail -- you're actually getting messages from two sources: (1) the MPICH library ("application called MPI_Abort...") and (2) the job launcher ("BAD TERMINATION..."). You can eliminate the messages from the job launcher by providing an error code of 0 in MPI_Abort.<div>
<br></div><div> ~Jim.<br><div><br></div><div><br></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Feb 21, 2014 at 1:19 PM, Jeff Hammond <span dir="ltr"><<a href="mailto:jeff.science@gmail.com" target="_blank">jeff.science@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">>> Just configure MPICH such that snprintf isn't discovered by configure<br>
>> and you won't see these messages.<br>
>><br>
>> The other solution is to fix PETSc so that people can't crash it so easily ;-)<br>
><br>
> 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.<br>
><br>
> 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.<br>
<br>
</div>You're returning a non-zero exit code, which I consider crashing. I<br>
apologize if this definition disagrees with yours. If this is just<br>
gentle cleanup, why not exit with code=0 as Jim suggested already?<br>
<div class="HOEnZb"><div class="h5"><br>
Jeff<br>
<br>
>> On Thu, Feb 20, 2014 at 3:19 PM, Jim Dinan <<a href="mailto:james.dinan@gmail.com">james.dinan@gmail.com</a>> wrote:<br>
>>> If you can find a way to call MPI_Finalize instead, you will portably<br>
>>> eliminate these messages.<br>
>>><br>
>>> A lesser solution would be to provide an error code of 0 (or MPI_SUCCESS) to<br>
>>> MPI_Abort, e.g. MPI_Comm_abort(MPI_COMM_WORLD, MPI_SUCCESS). This would<br>
>>> eliminate the error message that you are getting from the job launcher.<br>
>>> MPICH could be modified to be quiet about the abort when the application<br>
>>> aborts with an error code of MPI_SUCCESS.<br>
>>><br>
>>> ~Jim.<br>
>>><br>
>>><br>
>>> On Thu, Feb 20, 2014 at 12:33 PM, Barry Smith <<a href="mailto:bsmith@mcs.anl.gov">bsmith@mcs.anl.gov</a>> wrote:<br>
>>>><br>
>>>><br>
>>>> Is there any way to turn off MPICH (and others) printing messages about<br>
>>>> MPI_Abort? We have already prepared and presented useful error messages to<br>
>>>> the user about the situation and would like to avoid having these additional<br>
>>>> messages printed (that often make the situation look worse than it is)<br>
>>>><br>
>>>> Thanks<br>
>>>><br>
>>>> Barry<br>
>>>><br>
>>>> application called MPI_Abort(MPI_COMM_WORLD, 56) - process 0<br>
>>>> [cli_0]: aborting job:<br>
>>>> application called MPI_Abort(MPI_COMM_WORLD, 56) - process 0<br>
>>>><br>
>>>><br>
>>>> ==================================================================mailto:<a href="mailto:discuss@mpich.org">discuss@mpich.org</a>=================<br>
>>>> = BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES<br>
>>>> = EXIT CODE: 56<br>
>>>> = CLEANING UP REMAINING PROCESSES<br>
>>>> = YOU CAN IGNORE THE BELOW CLEANUP MESSAGES<br>
>>>><br>
>>>> ===================================================================================<br>
>>>><br>
>>>><br>
>>>><br>
>>>><br>
>>>> _______________________________________________<br>
>>>> discuss mailing list <a href="mailto:discuss@mpich.org">discuss@mpich.org</a><br>
>>>> To manage subscription options or unsubscribe:<br>
>>>> <a href="https://lists.mpich.org/mailman/listinfo/discuss" target="_blank">https://lists.mpich.org/mailman/listinfo/discuss</a><br>
>>><br>
>>><br>
>>><br>
>>> _______________________________________________<br>
>>> discuss mailing list <a href="mailto:discuss@mpich.org">discuss@mpich.org</a><br>
>>> To manage subscription options or unsubscribe:<br>
>>> <a href="https://lists.mpich.org/mailman/listinfo/discuss" target="_blank">https://lists.mpich.org/mailman/listinfo/discuss</a><br>
>><br>
>><br>
>><br>
>> --<br>
>> Jeff Hammond<br>
>> <a href="mailto:jeff.science@gmail.com">jeff.science@gmail.com</a><br>
>> _______________________________________________<br>
>> discuss mailing list <a href="mailto:discuss@mpich.org">discuss@mpich.org</a><br>
>> To manage subscription options or unsubscribe:<br>
>> <a href="https://lists.mpich.org/mailman/listinfo/discuss" target="_blank">https://lists.mpich.org/mailman/listinfo/discuss</a><br>
><br>
> _______________________________________________<br>
> discuss mailing list <a href="mailto:discuss@mpich.org">discuss@mpich.org</a><br>
> To manage subscription options or unsubscribe:<br>
> <a href="https://lists.mpich.org/mailman/listinfo/discuss" target="_blank">https://lists.mpich.org/mailman/listinfo/discuss</a><br>
<br>
<br>
<br>
--<br>
Jeff Hammond<br>
<a href="mailto:jeff.science@gmail.com">jeff.science@gmail.com</a><br>
_______________________________________________<br>
discuss mailing list <a href="mailto:discuss@mpich.org">discuss@mpich.org</a><br>
To manage subscription options or unsubscribe:<br>
<a href="https://lists.mpich.org/mailman/listinfo/discuss" target="_blank">https://lists.mpich.org/mailman/listinfo/discuss</a></div></div></blockquote></div><br></div>