I don't think so.
On Fri, Mar 30, 2012 at 9:39 PM, Barry Smith wrote:
>
> Do I have to rerun configure ?
>
> On Mar 30, 2012, at 9:35 PM, Dmitry Karpeev wrote:
>
> > Maybe that arch didn't get rebuilt? The HG time stamp in your stack
> trace says 'March 23'.
> > Hong alerted me to this bug tod
Do I have to rerun configure ?
On Mar 30, 2012, at 9:35 PM, Dmitry Karpeev wrote:
> Maybe that arch didn't get rebuilt? The HG time stamp in your stack trace
> says 'March 23'.
> Hong alerted me to this bug today and the fix is here:
> http://petsc.cs.iit.edu/petsc/petsc-dev/rev/de0779566bd
Maybe that arch didn't get rebuilt? The HG time stamp in your stack trace
says 'March 23'.
Hong alerted me to this bug today and the fix is here:
http://petsc.cs.iit.edu/petsc/petsc-dev/rev/de0779566bd9
Dmitry.
On Fri, Mar 30, 2012 at 9:27 PM, Barry Smith wrote:
>
> I will try again. But I jus
I will try again. But I just pulled before the test. Will see.
Barry
On Mar 30, 2012, at 9:21 PM, Dmitry Karpeev wrote:
> Barry,
> This looks like petsc-dev from about a week ago -- I fixed this bug today.
> It runs on my laptop right now.
>
> Dmitry.
>
> On Fri, Mar 30, 2012 at 9:00 PM
Barry,
This looks like petsc-dev from about a week ago -- I fixed this bug today.
It runs on my laptop right now.
Dmitry.
On Fri, Mar 30, 2012 at 9:00 PM, Barry Smith wrote:
>
> > [0]PETSC ERROR:
>
> > [0]PETSC ERROR: Caug
> [0]PETSC ERROR:
>
> [0]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation,
> probably memory access out of range
> [0]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger
> [0]PETSC ERROR
