Copying this to the list since it involves a coding error that is very
easy to make...
>> I think the following line is problematic:
>>
>> // Solucion actual del problema no lineal --> V
>> AutoPtr > V (system.solution);
>>
>> This constructs an AutoPtr "V" from the existing AutoPtr
>> system.solu
On Thu, 21 Jul 2011, John Peterson wrote:
> On Fri, Jul 15, 2011 at 5:37 PM, Joaquin Mura
> 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,
>>
On Fri, Jul 15, 2011 at 5:37 PM, Joaquin Mura 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