dolfin team mailing list archive

["Matthew Knepley" <knepley@xxxxxxxxx>]

On Thu, Sep 25, 2008 at 6:37 AM, Ilmar Wilbers <ilmarw@xxxxxxxxx> wrote:
> Now everything seems to be working except a petsc error:
> http://fenics.org:8010/dolfin/linux_32/builds/761/step-test/1
>
> I don't think this is because of the petsc setup, as all buildbots are
> experiencing the same

Its a memory protection error (SEGV). If it were inside PETSc however, it
would have the name of the method. It has "User function", so it happens
outside PETSc, but is caught by our signal handler. You can disable the
signal handler using PetscPopErrorHandler(). It is most likely that it is in
the interface to PETSc if it only occurs with those tests.

  Matt

> ilmar
>
> Garth N. Wells wrote:
>>
>>
>> Ilmar Wilbers wrote:
>>> Just a quick reminder about the fact that three python demos have
>>> been failing for som time now, please have a look at
>>> http://fenics.org:8010/dolfin/linux_32/builds/732/step-test/1
>>>
>>
>> These will probably remain broken for a few days until we get the
>> Function interface sorted out.
>>
>> Garth
>>
>>> ilmar
>>> _______________________________________________
>>> DOLFIN-dev mailing list
>>> DOLFIN-dev@xxxxxxxxxx
>>> http://www.fenics.org/mailman/listinfo/dolfin-dev
> _______________________________________________
> DOLFIN-dev mailing list
> DOLFIN-dev@xxxxxxxxxx
> http://www.fenics.org/mailman/listinfo/dolfin-dev
>



-- 
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