Error Handlers Function

[Santolo Felaco]

Hi, also with return; the handler function isn't called.


2009/2/26 Matthew Knepley <knepley at gmail.com>

> exit(2) does not trigger a PETSc error. SETERRQ does.
>
>   Matt
>
>
> On Thu, Feb 26, 2009 at 10:00 AM, Santolo Felaco <ahuramazda10 at gmail.com>wrote:
>
>> Hi,
>> I have setted a handler error function:
>> ierr = MPI_Errhandler_create(errorHandler,&errhandler); CHKERRQ(ierr);
>> ierr = MPI_Errhandler_set(PETSC_COMM_WORLD,errhandler); CHKERRQ(ierr);
>>
>> I have simulated a fault of processor 1:
>>
>> if (rank == 1)) exit(2);
>> MPI_Barrier(PETSC_COMM_WORLD);
>>
>> The process remains blocked and the functions errorHandler is not called.
>> 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.
>>
>> Help me please.
>>
>
>
>
> --
> What most experimenters take for granted before they begin their
> experiments is infinitely more interesting than any results to which their
> experiments lead.
> -- Norbert Wiener
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20090226/b216a881/attachment.htm>