> On Sep 21, 2015, at 7:30 PM, Roy Stogner 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 L
On Tue, Sep 22, 2015 at 12:10 PM, Barry Smith wrote:
>
> > On Sep 21, 2015, at 11:03 PM, David Knezevic
> wrote:
> >
> > On Tue, Sep 22, 2015 at 9:45 AM, Barry Smith wrote:
> >
> >
> https://bitbucket.org/petsc/petsc/issues/107/allow-recovery-from-certain-errors-in
> >
> >
> > This sounds like
> On Sep 21, 2015, at 11:03 PM, David Knezevic
> wrote:
>
> On Tue, Sep 22, 2015 at 9:45 AM, Barry Smith 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
On Tue, Sep 22, 2015 at 9:45 AM, Barry Smith 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
https://bitbucket.org/petsc/petsc/issues/107/allow-recovery-from-certain-errors-in
> On Sep 21, 2015, at 8:31 PM, David Knezevic
> wrote:
>
> On Tue, Sep 22, 2015 at 9:30 AM, Roy Stogner wrote:
>
> On Tue, 22 Sep 2015, David Knezevic wrote:
>
> I think it'd be good to make this easier t
On Tue, Sep 22, 2015 at 9:30 AM, Roy Stogner
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
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 inf
I use the solver library MUMPS via PETSc. Sometimes MUMPS fails due to
"error -9", which means that MUMPS allocated a workspace that wasn't big
enough. If you have MUMPS enabled, then you can reproduce this with
introduction_ex4 in libMesh as follows:
mpirun -np 4 ./example-opt -ksp_type preonly -
