Segmentation fault when using openmpi

Bug #224706 reported by ilmarw
This bug report is a duplicate of:  Bug #234837: Binutils corrupts Open MPI . Edit Remove
2
Affects Status Importance Assigned to Milestone
openmpi (Ubuntu)
New
Undecided
Unassigned

Bug Description

I have been trying to use openmpi for two different projects. On both, we swig the c source code and import it in python. These packages are dolfin, which we develop where I work, and the other is trilinos. In both cases, the output looks something like:
[multiboot:14707] *** Process received signal ***
[multiboot:14707] Signal: Segmentation fault (11)
[multiboot:14707] Signal code: Address not mapped (1)
[multiboot:14707] Failing at address: 0x8854004
[multiboot:14707] [ 0] [0xb7fbd440]
[multiboot:14707] [ 1] /usr/lib/libopen-pal.so.0(free+0xc4) [0xb5b6bae4]
[multiboot:14707] [ 2] /usr/lib/libopen-pal.so.0(mca_base_components_open+0x7f) [0xb5b5aabf]
[multiboot:14707] [ 3] /usr/lib/libopen-pal.so.0(opal_memory_base_open+0x44) [0xb5b6a3c4]
[multiboot:14707] [ 4] /usr/lib/libopen-pal.so.0(opal_init+0x9a) [0xb5b4f63a]
[multiboot:14707] [ 5] /usr/lib/libmpi.so.0(ompi_mpi_init+0x19) [0xb5c1e2b9]
[multiboot:14707] [ 6] /usr/lib/libmpi.so.0(MPI_Init+0xe7) [0xb5c41587]
[multiboot:14707] [ 7] /usr/lib/libpetsc.so.2.3.3(PetscInitialize+0x251) [0xb68c28ce]
[multiboot:14707] [ 8] /tmp/lib/libdolfin.so(_ZN6dolfin17SubSystemsManager9initPETScEiPPcb+0x98) [0xb5dea2c8]
[multiboot:14707] [ 9] /tmp/lib/libdolfin.so(_ZN6dolfin17SubSystemsManager9initPETScEv+0xaf) [0xb5dea44f]
[multiboot:14707] [10] /tmp/lib/libdolfin.so(_ZN6dolfin11PETScMatrixC1ENS0_4TypeE+0x27) [0xb5ddf3d7]
[multiboot:14707] [11] /tmp/lib/python2.5/site-packages/dolfin/_dolfin.so [0xb6ffa1ab]
[multiboot:14707] [12] python(PyObject_Call+0x27) [0x805cb37]
[multiboot:14707] [13] python(PyEval_EvalFrameEx+0x4064) [0x80c7ce4]
[multiboot:14707] [14] python(PyEval_EvalCodeEx+0x6e7) [0x80cb0d7]
[multiboot:14707] [15] python [0x8113430]
[multiboot:14707] [16] python(PyObject_Call+0x27) [0x805cb37]
[multiboot:14707] [17] python [0x8062b9b]
[multiboot:14707] [18] python(PyObject_Call+0x27) [0x805cb37]
[multiboot:14707] [19] python [0x809d26b]
[multiboot:14707] [20] python [0x809ee64]
[multiboot:14707] [21] python(PyObject_Call+0x27) [0x805cb37]
[multiboot:14707] [22] python(PyEval_EvalFrameEx+0x3d07) [0x80c7987]
[multiboot:14707] [23] python(PyEval_EvalCodeEx+0x6e7) [0x80cb0d7]
[multiboot:14707] [24] python(PyEval_EvalFrameEx+0x565e) [0x80c92de]
[multiboot:14707] [25] python(PyEval_EvalCodeEx+0x6e7) [0x80cb0d7]
[multiboot:14707] [26] python(PyEval_EvalCode+0x57) [0x80cb227]
[multiboot:14707] [27] python(PyRun_FileExFlags+0xf8) [0x80ea6d8]
[multiboot:14707] [28] python(PyRun_SimpleFileExFlags+0x199) [0x80ea979]
[multiboot:14707] [29] python(Py_Main+0xa35) [0x8059335]
[multiboot:14707] *** End of error message ***
Segmentation fault

When using the packages from debian sid, which uses version 1.2.6, it works. The weird thing is that if I apt-get source the code from ubuntu, and build the packages myself, it works as well. What can be done?

ilmar

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.