[petsc-users] problem running petsc4py

Hoang Giang Bui hgbk2008 at gmail.com
Wed Jan 2 08:09:01 CST 2013


Hi

When I ran the standard example of petsc4py, I got the error below

[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.
--------------------------------------------------------------------------
MPI_ABORT was invoked on rank 0 in communicator MPI_COMM_WORLD
with errorcode 59.

NOTE: invoking MPI_ABORT causes Open MPI to kill all MPI processes.
You may or may not see output from other processes, depending on
exactly when Open MPI kills them.

Moreover, printing out the value of Istart and Iend returns 0 (at 
A.getOwnershipRange())

Please advise the root cause of this problem. I compiled petsc4py-dev 
against petsc-3.3-p5 in debug mode.

BR
Giang Bui

-------------- next part --------------
A non-text attachment was scrubbed...
Name: ex1.py
Type: text/x-python
Size: 1701 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20130102/16b81180/attachment.py>


More information about the petsc-users mailing list