> On Sep 21, 2015, at 11:03 PM, David Knezevic <david.kneze...@akselos.com> > wrote: > > On Tue, Sep 22, 2015 at 9:45 AM, Barry Smith <bsm...@mcs.anl.gov> wrote: > > > https://bitbucket.org/petsc/petsc/issues/107/allow-recovery-from-certain-errors-in > > > This sounds like the ideal fix. Would you plan to make this available in > 3.6.x? If it will be a long time before it's available in a release version > of PETSc, then I'll still go ahead with Roy's suggestion of changing > LIBMESH_CHKERRABORT, I think.
It be until the next release. Yes, it makes sense for you to do a more direct short term fix. Let us know if you have any trouble with the PETSc error call. Barry > > David > > > > > > On Sep 21, 2015, at 8:31 PM, David Knezevic <david.kneze...@akselos.com> > > wrote: > > > > On Tue, Sep 22, 2015 at 9:30 AM, Roy Stogner <royst...@ices.utexas.edu> > > wrote: > > > > On Tue, 22 Sep 2015, David Knezevic wrote: > > > > I think it'd be good to make this easier to recover from, e.g. we could > > throw an > > exception instead of calling LIBMESH_CHKERRABORT(ierr)? > > > > Would it make sense to just redefine LIBMESH_CHKERRABORT to throw an > > exception (after pulling whatever string info we can get from PETSc > > about the nature of the error)? > > > > > > That sounds good to me. > > > > David > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > > Libmesh-devel mailing list > > Libmesh-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/libmesh-devel > > ------------------------------------------------------------------------------ _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
