1e5c89e4eSSatish Balay /* 2e5c89e4eSSatish Balay The default error handlers and code that allows one to change 3e5c89e4eSSatish Balay error handlers. 4e5c89e4eSSatish Balay */ 5c6db04a5SJed Brown #include <petscsys.h> /*I "petscsys.h" I*/ 6e5c89e4eSSatish Balay 7e5c89e4eSSatish Balay /*@C 8e5c89e4eSSatish Balay PetscAbortErrorHandler - Error handler that calls abort on error. 9e5c89e4eSSatish Balay This routine is very useful when running in the debugger, because the 10e5c89e4eSSatish Balay user can look directly at the stack frames and the variables. 11e5c89e4eSSatish Balay 12e5c89e4eSSatish Balay Not Collective 13e5c89e4eSSatish Balay 14e5c89e4eSSatish Balay Input Parameters: 15e32f2f54SBarry Smith + comm - communicator over which error occurred 16e32f2f54SBarry Smith . line - the line number of the error (indicated by __LINE__) 17e5c89e4eSSatish Balay . file - the file in which the error was detected (indicated by __FILE__) 18e5c89e4eSSatish Balay . mess - an error text string, usually just printed to the screen 19e5c89e4eSSatish Balay . n - the generic error number 20e5c89e4eSSatish Balay . p - specific error number 21e5c89e4eSSatish Balay - ctx - error handler context 22e5c89e4eSSatish Balay 23e5c89e4eSSatish Balay Options Database Keys: 24e5c89e4eSSatish Balay + -on_error_abort - Activates aborting when an error is encountered 25e5c89e4eSSatish Balay - -start_in_debugger [noxterm,dbx,xxgdb] [-display name] - Starts all 26e5c89e4eSSatish Balay processes in the debugger and uses PetscAbortErrorHandler(). By default the 27e5c89e4eSSatish Balay debugger is gdb; alternatives are dbx and xxgdb. 28e5c89e4eSSatish Balay 29e5c89e4eSSatish Balay Level: developer 30e5c89e4eSSatish Balay 31e5c89e4eSSatish Balay Notes: 32e5c89e4eSSatish Balay Most users need not directly employ this routine and the other error 33e5c89e4eSSatish Balay handlers, but can instead use the simplified interface SETERRQ, which 34e5c89e4eSSatish Balay has the calling sequence 35e32f2f54SBarry Smith $ SETERRQ(comm,number,mess) 3698921bdaSJacob Faibussowitsch or its variants, SETERRQ(number,formatstring,arg1), SETERRQ(), ... that 37e5c89e4eSSatish Balay allow including arguments in the message. 38e5c89e4eSSatish Balay 39e5c89e4eSSatish Balay Notes for experienced users: 40e5c89e4eSSatish Balay Use PetscPushErrorHandler() to set the desired error handler. The 41e5c89e4eSSatish Balay currently available PETSc error handlers include PetscTraceBackErrorHandler(), 42e5c89e4eSSatish Balay PetscAttachDebuggerErrorHandler(), and PetscAbortErrorHandler(). 43e5c89e4eSSatish Balay 44db781477SPatrick Sanan .seealso: `PetscError()`, `PetscPushErrorHandler()`, `PetscPopErrorHander()`, `PetscTraceBackErrorHandler()`, 45db781477SPatrick Sanan `PetscAttachDebuggerErrorHandler()`, `PetscMPIAbortErrorHandler()`, `PetscReturnErrorHandler()`, `PetscEmacsClientErrorHandler()` 46e5c89e4eSSatish Balay @*/ 47*9371c9d4SSatish Balay PetscErrorCode PetscAbortErrorHandler(MPI_Comm comm, int line, const char *fun, const char *file, PetscErrorCode n, PetscErrorType p, const char *mess, void *ctx) { 48e5c89e4eSSatish Balay PetscFunctionBegin; 492f307e7aSJunchao Zhang (*PetscErrorPrintf)("PetscAbortErrorHandler: %s() at %s:%d %s\n To prevent termination, change the error handler using PetscPushErrorHandler()\n", fun, file, line, mess); 50e5c89e4eSSatish Balay abort(); 51e5c89e4eSSatish Balay PetscFunctionReturn(0); 52e5c89e4eSSatish Balay } 53