[petsc-users] Error: likely due to memory corruption

[Yongxiang Wu]

Hello PETSC users:
i am using slepc4py to compute a geenral eigenvalue problem.  I have
compiled PETSC/SLEPC and petsc4py/slepc4py on a cray cluster (hazelhen).
When I run my test case, I get the following error. Would anyone provide me
the direction to solve it?

regards
Yong

Slepsc begins ...
Parallel read in petsc binary matrix for each processor!!!
load petsc binary finished
Start solving ...
[0]PETSC ERROR: [2]PETSC ERROR:
------------------------------------------------------------------------
[5]PETSC ERROR:
------------------------------------------------------------------------
[0]PETSC ERROR: [2]PETSC ERROR: [1]PETSC ERROR:
------------------------------------------------------------------------
Caught signal number 4 Illegal instruction: Likely due to memory corruption
Caught signal number 4 Illegal instruction: Likely due to memory corruption
[5]PETSC ERROR: [0]PETSC ERROR: [2]PETSC ERROR:
------------------------------------------------------------------------
Try option -start_in_debugger or -on_error_attach_debugger
Try option -start_in_debugger or -on_error_attach_debugger
[1]PETSC ERROR: [2]PETSC ERROR: [0]PETSC ERROR: or see
http://www.mcs.anl.gov/petsc/documentation/faq.html#valgrind
Caught signal number 4 Illegal instruction: Likely due to memory corruption
Caught signal number 4 Illegal instruction: Likely due to memory corruption
[5]PETSC ERROR: or see
http://www.mcs.anl.gov/petsc/documentation/faq.html#valgrind
[0]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger
[1]PETSC ERROR: [2]PETSC ERROR: or try http://valgrind.org on GNU/linux and
Apple Mac OS X to find memory corruption errors
[5]PETSC ERROR: [3]PETSC ERROR: [4]PETSC ERROR:
------------------------------------------------------------------------
Try option -start_in_debugger or -on_error_attach_debugger
------------------------------------------------------------------------
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: or see
http://www.mcs.anl.gov/petsc/documentation/faq.html#valgrind
[3]PETSC ERROR: [1]PETSC ERROR: Caught signal number 4 Illegal instruction:
Likely due to memory corruption
or see http://www.mcs.anl.gov/petsc/documentation/faq.html#valgrind
[3]PETSC ERROR: [4]PETSC ERROR: [2]PETSC ERROR: Caught signal number 4
Illegal instruction: Likely due to memory corruption
configure using --with-debugging=yes, recompile, link, and run
[2]PETSC ERROR: to get more information on the crash.
to get more information on the crash.
[5]PETSC ERROR: [1]PETSC ERROR: Try option -start_in_debugger or
-on_error_attach_debugger
[4]PETSC ERROR: or try http://valgrind.org on GNU/linux and Apple Mac OS X
to find memory corruption errors
or try http://valgrind.org on GNU/linux and Apple Mac OS X to find memory
corruption errors
[3]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger
[5]PETSC ERROR: [1]PETSC ERROR: or see
http://www.mcs.anl.gov/petsc/documentation/faq.html#valgrind
[4]PETSC ERROR: configure using --with-debugging=yes, recompile, link, and
run
configure using --with-debugging=yes, recompile, link, and run
[3]PETSC ERROR: or see
http://www.mcs.anl.gov/petsc/documentation/faq.html#valgrind
[5]PETSC ERROR: to get more information on the crash.
[1]PETSC ERROR: or try http://valgrind.org on GNU/linux and Apple Mac OS X
to find memory corruption errors
[4]PETSC ERROR: to get more information on the crash.
[3]PETSC ERROR: or try http://valgrind.org on GNU/linux and Apple Mac OS X
to find memory corruption errors
configure using --with-debugging=yes, recompile, link, and run
[4]PETSC ERROR: [3]PETSC ERROR: configure using --with-debugging=yes,
recompile, link, and run
to get more information on the crash.
[4]PETSC ERROR: to get more information on the crash.
Rank 2 [Tue Apr 24 14:17:09 2018] [c4-3c2s4n2] application called
MPI_Abort(MPI_COMM_WORLD, 59) - process 2
Rank 0 [Tue Apr 24 14:17:09 2018] [c4-3c2s4n2] application called
MPI_Abort(MPI_COMM_WORLD, 59) - process 0
Rank 5 [Tue Apr 24 14:17:09 2018] [c4-3c2s4n2] application called
MPI_Abort(MPI_COMM_WORLD, 59) - process 5
Rank 1 [Tue Apr 24 14:17:09 2018] [c4-3c2s4n2] application called
MPI_Abort(MPI_COMM_WORLD, 59) - process 1
Rank 3 [Tue Apr 24 14:17:09 2018] [c4-3c2s4n2] application called
MPI_Abort(MPI_COMM_WORLD, 59) - process 3
Rank 4 [Tue Apr 24 14:17:09 2018] [c4-3c2s4n2] application called
MPI_Abort(MPI_COMM_WORLD, 59) - process 4
_pmiu_daemon(SIGCHLD): [NID 07826] [c4-3c2s4n2] [Tue Apr 24 14:17:09 2018]
PE RANK 0 exit signal Aborted
[NID 07826] 2018-04-24 14:17:09 Apid 298658: initiated application
termination
Application 298658 exit codes: 134
Application 298658 resources: utime ~6s, stime ~2s, Rss ~488036, inblocks
~862, outblocks ~0
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20180424/1eaef2ef/attachment.html>