[petsc-users] sigsegvs

[Matthew Knepley]

On Sun, Jul 22, 2012 at 9:22 PM, Juha Jäykkä <juhaj at iki.fi> wrote:

> Hi list!
>
> Petsc3.2-p7, make test fails and at a closer look,
> src/snes/examples/tutorials/ex19 gives:
>

Is this complex? There was a problem with the complex dot product for some
BLAS. If this is the problem, you can reconfigure with
--download-f-blas-lapack.
Also, upgrading should fix it.

   Matt


> orterun -n 1 ./ex19 -dmmg_nlevels 4 -snes_monitor_short -
> on_error_attach_debugger
> lid velocity = 0.0016, prandtl # = 1, grashof # = 1
> [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: or see http://www.mcs.anl.gov/petsc/petsc-
> as/documentation/faq.html#valgrind[0]PETSC ERROR: or try
> http://valgrind.org
> on GNU/linux and Apple Mac OS X to find memory corruption errors
> [0]PETSC ERROR: likely location of problem given in stack below
> [0]PETSC ERROR: ---------------------  Stack Frames
> ------------------------------------
> [0]PETSC ERROR: Note: The EXACT line numbers in the stack are not
> available,
> [0]PETSC ERROR:       INSTEAD the line number of the start of the function
> [0]PETSC ERROR:       is given.
> [0]PETSC ERROR: [0] VecNorm_Seq line 236 src/vec/vec/impls/seq/bvec2.c
> [0]PETSC ERROR: [0] VecNormBegin line 479 src/vec/vec/utils/comb.c
> [0]PETSC ERROR: [0] SNESSolve_LS line 142 src/snes/impls/ls/ls.c
> [0]PETSC ERROR: [0] SNESSolve line 2647 src/snes/interface/snes.c
> [0]PETSC ERROR: [0] DMMGSolveSNES line 538 src/snes/utils/damgsnes.c
> [0]PETSC ERROR: [0] DMMGSolve line 303 src/snes/utils/damg.c
> [0]PETSC ERROR: User provided function() line 0 in unknown directory
> unknown
> file
> --------------------------------------------------------------------------
>
> Any idea where this could come from? Worst of all, if I run this in
> debugger,
> it never sigsegvs, likewise under valgrind. Sometimes (about 1/3) it also
> succeeds without a debugger, but even when not segfaulting, it gives wrong
> results (so I assume not segfaulting is just good (or bad?) luck):
>
> 2,5c2,3
> <   0 SNES Function norm 0.0406612
> <   1 SNES Function norm 3.33175e-06
> <   2 SNES Function norm 1.092e-11
> < Number of Newton iterations = 2
> ---
> >   0 SNES Function norm < 1.e-11
> > Number of Newton iterations = 0
> 7,10c5,6
> <   0 SNES Function norm 0.0406612
> <   1 SNES Function norm 3.33175e-06
> <   2 SNES Function norm 1.092e-11
> < Number of Newton iterations = 2
> ---
> >   0 SNES Function norm < 1.e-11
> > Number of Newton iterations = 0
>
> Any help appreciated, thanks.
> Juha
>
> --
>                  -----------------------------------------------
>                 | Juha Jäykkä, juhaj at iki.fi                     |
>                 | http://koti.kapsi.fi/~juhaj/                  |
>                  -----------------------------------------------
>



-- 
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/20120722/580e87c3/attachment.html>