Re: [Libmesh-users] [Libmesh-devel] A question about the use of Libmesh

[Roy S. <roy...@ic...>]

On Thu, 21 Jul 2011, John Peterson wrote:

> On Fri, Jul 15, 2011 at 5:37 PM, Joaquin Mura <joa...@ho...> wrote:
>>
>> The first iteration runs ok, but the second iteration stops during the call
>> to solve(), throwing the message:
>> [0]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation,
>> probably memory access out of range
>>
>> Debugging with gdb, I only get that the error is produced during the
>> execution
>> of "libMesh::PetscLinearSolver<double>::solve( ..."
>
> We'd need to see the code itself to pinpoint the error,

John isn't just subtly hinting here that we'd like you to contribute
an elasticity example app... but actually, we *could* use linear and
nonlinear elasticity example apps.  ;-)

But more practical advice for Joaquin: are you running a METHOD=devel
(or preferably debug, if you can tolerate it being dog-slow) build of
libMesh linked against a --with-debugging build of PETSc?  Often these
sorts of errors can be caught before they snowball to the point of
writing outside of allocated memory.
---
Roy