Open MPI logo

Open MPI User's Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Open MPI User's mailing list

Subject: Re: [OMPI users] Segmentation fault: Address not mapped
From: James Philbin (james_at_[hidden])
Date: 2008-07-30 08:31:37


Hi,

OK, to answer my own question, I recompiled OpenMPI appending
'--with-memory-manager=none' to configure and now things seem to run
fine. I'm not sure how this might affect performance, but at least
it's working now. Maybe this can be put in the FAQ?

James

On Wed, Jul 30, 2008 at 2:02 AM, James Philbin <james_at_[hidden]> wrote:
> Hi,
>
> I'm running an mpi module in python (pypar), but I believe (after
> googling) that this might be a problem with openmpi.
> When I run: 'python -c "import pypar"', I get:
> [titus:21965] *** Process received signal ***
> [titus:21965] Signal: Segmentation fault (11)
> [titus:21965] Signal code: Address not mapped (1)
> [titus:21965] Failing at address: 0x837a004
> [titus:21965] [ 0] /lib/i686/libpthread.so.0 [0x40035f93]
> [titus:21965] [ 1] python [0x42029180]
> [titus:21965] [ 2] /users/james/lib/libopen-pal.so.0(free+0xbc) [0x40e112fc]
> [titus:21965] [ 3]
> /users/james/lib/libopen-pal.so.0(mca_base_components_open+0x83)
> [0x40dff9b3]
> [titus:21965] [ 4]
> /users/james/lib/libmpi.so.0(mca_allocator_base_open+0x46)
> [0x40cb03b6]
> [titus:21965] [ 5] /users/james/lib/libmpi.so.0(ompi_mpi_init+0x3dd)
> [0x40c7b7dd]
> [titus:21965] [ 6] /users/james/lib/libmpi.so.0(MPI_Init+0xef) [0x40c9fb1f]
> [titus:21965] [ 7]
> /users/james/lib/python2.5/site-packages/pypar/mpiext.so [0x40576613]
> [titus:21965] [ 8] python(PyCFunction_Call+0x5a) [0x810c9ea]
> [titus:21965] [ 9] python [0x80bb2fb]
> [titus:21965] [10] python(PyEval_EvalFrameEx+0x22d2) [0x80b97a2]
> [titus:21965] [11] python(PyEval_EvalCodeEx+0x376) [0x80ba0b6]
> [titus:21965] [12] python(PyEval_EvalCode+0x57) [0x80bcfe7]
> [titus:21965] [13] python(PyImport_ExecCodeModuleEx+0x13a) [0x80d0b9a]
> [titus:21965] [14] python [0x80d3eeb]
> [titus:21965] [15] python [0x80d180e]
> [titus:21965] [16] python [0x80d27b6]
> [titus:21965] [17] python [0x80d2309]
> [titus:21965] [18] python [0x80d45bf]
> [titus:21965] [19] python(PyImport_ImportModuleLevel+0x90) [0x80d3a40]
> [titus:21965] [20] python [0x80b3dda]
> [titus:21965] [21] python(PyCFunction_Call+0xce) [0x810ca5e]
> [titus:21965] [22] python(PyObject_Call+0x29) [0x805eca9]
> [titus:21965] [23] python(PyEval_CallObjectWithKeywords+0x75) [0x80bae95]
> [titus:21965] [24] python(PyEval_EvalFrameEx+0x2041) [0x80b9511]
> [titus:21965] [25] python(PyEval_EvalCodeEx+0x376) [0x80ba0b6]
> [titus:21965] [26] python(PyEval_EvalCode+0x57) [0x80bcfe7]
> [titus:21965] [27] python(PyImport_ExecCodeModuleEx+0x13a) [0x80d0b9a]
> [titus:21965] [28] python [0x80d3eeb]
> [titus:21965] [29] python [0x80d180e]
>
> I've built openmpi from the 1.2.6 sources with the following configure
> flag: './configure --disable-dlopen --prefix=/users/james'.
>
> pypar seems to work fine on my ubuntu system also with openmpi
> (installed from repositories). I'm tearing my hair out trying to solve
> this, so any advice would be very welcome.
>
> Thanks,
> James
>