[petsc-dev] Possible error running C/C++ src/snes/examples/tutorials/ex19 with 1 MPI process

[Satish Balay]

On Fri, 7 Oct 2016, Matthew Knepley wrote:

> On Fri, Oct 7, 2016 at 10:54 AM, Antonio Trande <anto.trande at gmail.com>
> wrote:
> 
> > Hi all.
> >
> > This issue is related to discussion from dev-ML:
> > http://lists.mcs.anl.gov/pipermail/petsc-dev/2016-October/019827.html
> >
> > What do cause the errors:
> >
> > + make -C build64 test
> > make: Entering directory '/builddir/build/BUILD/petsc-3.7.3/build64'
> > Running test examples to verify correct installation
> > Using PETSC_DIR=/builddir/build/BUILD/petsc-3.7.3/build64 and
> > PETSC_ARCH=x86_64
> > /usr/bin/sh: line 20: 14262 Aborted                 (core dumped)
> > /builddir/build/BUILD/petsc-3.7.3/build64/bin/petsc-mpiexec.uni -n 1
> > ./ex19 -da_refine 3 -pc_type mg -ksp_type fgmres > ex19_1.tmp 2>&1
> > Possible error running C/C++ src/snes/examples/tutorials/ex19 with 1 MPI
> > process
> >
> 
> Run with -start_in_debugger and give us the stack trace


Or valgrind - which should be scriptable..

make test MPIEXEC='$PETSC_DIR/bin/petscmpiexec -valgrind'

Satish

> 
>   Thanks,
> 
>     Matt
> 
> 
> > See http://www.mcs.anl.gov/petsc/documentation/faq.html
> > 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/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: configure using --with-debugging=yes, recompile, link,
> > and run
> > [0]PETSC ERROR: to get more information on the crash.
> > [0]PETSC ERROR: --------------------- Error Message
> > --------------------------------------------------------------
> > [0]PETSC ERROR: Signal received
> > [0]PETSC ERROR: See http://www.mcs.anl.gov/petsc/documentation/faq.html
> > for trouble shooting.
> > [0]PETSC ERROR: Petsc Release Version 3.7.3, Jul, 24, 2016
> >
> > ?
> >
> > They come out by testing serial PETSc libraries according to reported
> > configuration in following log, please, see
> > https://paste.fedoraproject.org/445643/
> >
> > Starting from line #8, is tested 'libpetsc.so'.
> > Starting from line #162, is tested 'libpetsc64.so' (with 64bit indices).
> >
> >
> > --
> > ---
> > Antonio Trande
> > mailto: sagitter 'at' fedoraproject 'dot' org
> > http://fedoraos.wordpress.com/
> > https://fedoraproject.org/wiki/User:Sagitter
> > GPG Key: 0x6CE6D08A
> > Check on https://keys.fedoraproject.org/
> >
> >
> 
> 
>