Hi, also with return; the handler function isn't called.<br><br><br><div class="gmail_quote">2009/2/26 Matthew Knepley <span dir="ltr"><<a href="mailto:knepley@gmail.com">knepley@gmail.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
exit(2) does not trigger a PETSc error. SETERRQ does.<br><br> Matt<div><div></div><div class="Wj3C7c"><br><br><div class="gmail_quote">On Thu, Feb 26, 2009 at 10:00 AM, Santolo Felaco <span dir="ltr"><<a href="mailto:ahuramazda10@gmail.com" target="_blank">ahuramazda10@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi,<br>I have setted a handler error function:<br>ierr = MPI_Errhandler_create(errorHandler,&errhandler); CHKERRQ(ierr);<br>
ierr = MPI_Errhandler_set(PETSC_COMM_WORLD,errhandler); CHKERRQ(ierr);<br><br>I have simulated a fault of processor 1:<br>
<br>if (rank == 1)) exit(2); <br>MPI_Barrier(PETSC_COMM_WORLD); <br><br>The process remains blocked and the functions errorHandler is not called.<br>If I use return; instead of exit(2); the process don't remains blocked, I read the error of Petsc but errorHandler is not called.<br>
<br>Help me please.<br>
</blockquote></div><br><br clear="all"><br></div></div><font color="#888888">-- <br>What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead.<br>
-- Norbert Wiener<br>
</font></blockquote></div><br>