>>>>> Configure Options: --configModules=PETSc.Configure --optionsModule=PETSc.compilerOptions --with-cc=gcc --with-fc=gfortran --with-cxx=g++ --with-mpi=0 --with-x=0 --with-clanguage=cxx --with-shared=1 --with-dynamic=1 PETSC_ARCH=x86_64_linux_node2 <<<<<<
We don't won't to flood mailing lists with huge attachments - so emails with configure.log attachments will be blocked. [petsc-maint would be the correct place for such e-mails]. In your case - if the code runs fine in debugger - but not directly - it could mean some random memory corruption error. Sugest using valgrind to narrow down the problem. i.e valgrind --tool=memcheck -q binary Satish On Thu, 12 Feb 2009, Wei-Dong Lian wrote: > Hello everyone, > I am new for petsc. Thanks a lot for everyone working on petsc. It is really > powerful and stable. > I met a problem in using petsc. Below are the error information. But when I > run this program under gdb degbuger, it worked. and the results are OK. > I am attaching the configure.log and make.log of petsc. > Can anyone give me some suggestions, I will be appreciated. > Thanks a lot. > > [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/troubleshooting.html#Signal[0]PETSCERROR: > or try > http://valgrind.org on linux or man libgmalloc on Apple 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: --------------------- Error Message > ------------------------------------ > [0]PETSC ERROR: Signal received! > [0]PETSC ERROR: > ------------------------------------------------------------------------ > [0]PETSC ERROR: Petsc Release Version 3.0.0, Patch 3, Fri Jan 30 17:55:56 > CST 2009 > [0]PETSC ERROR: See docs/changes/index.html for recent updates. > [0]PETSC ERROR: See docs/faq.html for hints about trouble shooting. > [0]PETSC ERROR: See docs/index.html for manual pages. > [0]PETSC ERROR: > ------------------------------------------------------------------------ > [0]PETSC ERROR: ./main on a x86_64_li named node2.alineos.net by lian Thu > Feb 12 16:23:38 2009 > [0]PETSC ERROR: Libraries linked from > /glouton/struct/lian/develop-64/Solver/petscSeq/x86_64_linux_node2/lib > [0]PETSC ERROR: Configure run at Thu Feb 12 11:20:04 2009 > [0]PETSC ERROR: Configure options --with-cc=gcc --with-fc=gfortran > --with-cxx=g++ --with-mpi=0 --with-x=0 --with-clanguage=cxx --with-shared=1 > --with-dynamic=1 PETSC_ARCH=x86_64_linux_node2 > [0]PETSC ERROR: > ------------------------------------------------------------------------ > [0]PETSC ERROR: User provided function() line 0 in unknown directory unknown > file > /bin/sh: line 1: 27527 Aborted ./main data/main.dat >
