On Wed, 25 May 2011, Derek Gaston wrote:
> I like the idea of adding a handler for segfaults that writes a
> stack trace! Especially if it overrides the Petsc error handlers.
> It wouldn't be helpful in this particular case because I already got
> the stack trace with a core dump... but it woul
On May 25, 2011, at 12:54 PM, Roy Stogner wrote:
> I really wish you'd stopped after "reproducible"...
Heh... me too!
>> 2. Using the old System::update() with a solution->close() at the
>> beginning is _not_ sufficient! It still segfaults!
>
> This is astonishing.
>
> This is on PETSc 2.3.3
On Mon, 23 May 2011, Derek Gaston wrote:
Here's some more info on this subject:
1. The old System::update() is really segfaulting. It's pretty reproducible
with ~60 million DoFs.
I really wish you'd stopped after "reproducible"...
2. Using the old System::update() with a solution->close
On Wed, 18 May 2011, Derek Gaston wrote:
>>> It would be cruel... BUT, I had a user in my office just yesterday
>>> that wanted to have overlapping subdomains. I think for now we're
>>> going to deal with it using an external file that defines the
>>> overlaps and deal with it manually... but t
