[petsc-users] seg fault with VecGetArray

[Matthew Knepley]

On Sat, May 12, 2012 at 4:33 AM, Mohammad Mirzadeh <mirzadeh at gmail.com>wrote:

> Hi guys,
>
> I'm having a really weird issue here! My code seg faults for certain
> problem size and after using gdb I have been able to pinpoint the problem
> to a VecGetArray call. Here's a series of things I have tried so far
>
> 1) -on_error_attach_debugger -----> unsuccessful; does not launch debugger
> 2) -start_in_debugger -------> unsuccessful; does not start debugger
>

Run with -log_summary. It will tell you what options the program got. Also,
are there errors relating to X? Send
all output to petsc-maint at mcs.anl.gov


> 3) attaching debugger myself -----> code runs in debugger and seg faults
> when calling VecGetArray
>

Is this a debug build? What dereference is causing the SEGV? Is the Vec a
valid object? It sounds like
it has been corrupted.


> 4) using ierr=VecGetArray;CHKERRQ(ierr) ------> PETSc does not produce
> error messages; the code simply seg faults and terminates
> 5) checking the values of ierr inside the debugger ---------> They are all
> 0 up untill the code terminates; I think this means petsc does not generate
> error?
> 6) checking for memory leak with valgrind -----------> All I get are leaks
> from OpenMPI and PetscInitialize and PetscFinalize; I think these are
> just routine and safe?
>

How can we say anything without the valgrind output?

    Matt


>
> What else can I try to find the problem? Any recommendation is really
> appreciated!
>
> Thanks,
> Mohammad
>



-- 
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20120512/c0fbe9c3/attachment.htm>