Searched refs:handlers (Results 1 – 7 of 7) sorted by relevance
85 - PETSc error handlers now trap many more signals.
168 - PETSc error handlers now take two additional arguments. Consult
32 …e (0) would be propagated as-is. Note that while returning 0 from error handlers in `PetscError()`…
113 handlers. The most recent error handler is removed via116 PETSc provides several default error handlers:
4541 MatSolverTypeForSpecifcType handlers; member4574 PetscCall(PetscNew(&MatSolverTypeHolders->handlers)); in MatSolverTypeRegister()4575 PetscCall(PetscStrallocpy(mtype, (char **)&MatSolverTypeHolders->handlers->mtype)); in MatSolverTypeRegister()4576 MatSolverTypeHolders->handlers->createfactor[(int)ftype - 1] = createfactor; in MatSolverTypeRegister()4582 …PetscCheck(next->handlers, PETSC_COMM_SELF, PETSC_ERR_PLIB, "MatSolverTypeHolder is missing handle… in MatSolverTypeRegister()4583 inext = next->handlers; in MatSolverTypeRegister()4603 PetscCall(PetscNew(&prev->next->handlers)); in MatSolverTypeRegister()4604 PetscCall(PetscStrallocpy(mtype, (char **)&prev->next->handlers->mtype)); in MatSolverTypeRegister()4605 prev->next->handlers->createfactor[(int)ftype - 1] = createfactor; in MatSolverTypeRegister()4653 inext = next->handlers; in MatSolverTypeGet()[all …]
214 """Clear all the option handlers.
441 checks a stack of error handlers and calls the one on the top. If the460 PETSc provides two additional error handlers besides471 handlers can be set with the options `-on_error_abort` or