← Back to team overview

dolfin team mailing list archive

Re: problems compiling dolfin_wrap.cc with mpicxx (g++) 4.3.1

 

Thanks for your reply Garth. I get a seg fault when I run the poisson demo:

~/computer/fenics/dolfin/dolfin/demo/pde/poisson/python$ python demo.py
Segmentation fault

No other information is given. Any ideas? Should I just forget about
the Python interface until someone fixes swig upstream?

Thanks,
Tim


On Mon, Aug 25, 2008 at 3:01 PM, Garth N. Wells <gnw20@xxxxxxxxx> wrote:
>
>
> Timothy Crone wrote:
>>
>> Hello,
>>
>> Does anyone know a workaround to the problem of compiling the Pydolfin
>> file dolfin_wrap.cc with mpicxx version 4.3.1? I get several warnings
>> during compile, and segmentation faults at runtime. I am using Debian
>> Lenny, which uses 4.3.1 as the default compiler. SWIG is version
>> 1.3.33. Any help in this matter would be greatly appreciated.
>>
>
> It's a swig problem that leads to the errors as far I see and I don't think
> that there's much we can do about it. I wouldn't expect it to lead to seg
> faults though. When exactly to you get a seg fault?
>
> Garth
>
>> Here are the errors when enableDebug=no:
>>
>> mpicxx -o dolfin/swig/dolfin_wrap.os -c -Wall -pipe -ansi -DNDEBUG -O3
>> -DHAS_MPI=1 -DMPICH_IGNORE_CXX_SEEK -DPACKAGE_VERSION=\"0.8.0\"
>> -DHAS_PETSC=1 -DHAS_UMFPACK=1 -DHAS_GTS=1 -DHAS_CHOLMOD=1
>> -fno-strict-aliasing -fPIC -I. -I/usr/include/libxml2
>> -I/usr/lib/petscdir/2.3.3/bmake/linux-gnu-c-opt
>> -I/usr/lib/petscdir/2.3.3/include -I/usr/lib/openmpi/include
>> -I/usr/lib/openmpi/lib -Idolfin -I/usr/include/suitesparse
>> -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
>> -I/usr/include/suitesparse -I/usr/include/python2.5
>> -I/usr/include/python2.5
>> -I/usr/lib/python2.5/site-packages/numpy/core/include
>> -I/usr/include/libxml2 -I/usr/lib/petscdir/2.3.3/bmake/linux-gnu-c-opt
>> -I/usr/lib/petscdir/2.3.3/include -I/usr/lib/openmpi/include
>> -I/usr/lib/openmpi/lib -Idolfin -I/usr/include/suitesparse
>> -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
>> -I/usr/include/suitesparse dolfin/swig/dolfin_wrap.cc
>> dolfin/swig/dolfin_wrap.cc: In constructor
>> 'swig::PyObject_ptr::PyObject_ptr(PyObject*, bool)':
>> dolfin/swig/dolfin_wrap.cc:3286: warning: suggest explicit braces to
>> avoid ambiguous 'else'
>> dolfin/swig/dolfin_wrap.cc: In destructor
>> 'swig::PySequence_Cont<T>::~PySequence_Cont()':
>> dolfin/swig/dolfin_wrap.cc:4727: warning: suggest explicit braces to
>> avoid ambiguous 'else'
>> dolfin/swig/dolfin_wrap.cc: In function 'PyObject*
>> _wrap_summary(PyObject*, PyObject*)':
>> dolfin/swig/dolfin_wrap.cc:29893: warning: 'argv[0]' may be used
>> uninitialized in this function
>> dolfin/swig/dolfin_wrap.cc: In function 'PyObject*
>> _wrap_ios_base_sync_with_stdio(PyObject*, PyObject*)':
>> dolfin/swig/dolfin_wrap.cc:17337: warning: 'argv[0]' may be used
>> uninitialized in this function
>> dolfin/swig/dolfin_wrap.cc: In function 'PyObject*
>> _wrap_new_TimeDependent(PyObject*, PyObject*)':
>> dolfin/swig/dolfin_wrap.cc:28067: warning: 'argv[0]' may be used
>> uninitialized in this function
>> dolfin/swig/dolfin_wrap.cc: In function 'PyObject*
>> _wrap_new_BoundaryMesh(PyObject*, PyObject*)':
>> dolfin/swig/dolfin_wrap.cc:90450: warning: 'argv[0]' may be used
>> uninitialized in this function
>> dolfin/swig/dolfin_wrap.cc: In function 'PyObject*
>> _wrap_new_MeshTopology(PyObject*, PyObject*)':
>> dolfin/swig/dolfin_wrap.cc:74482: warning: 'argv[0]' may be used
>> uninitialized in this function
>> dolfin/swig/dolfin_wrap.cc: In function 'PyObject*
>> _wrap_new_MeshConnectivity(PyObject*, PyObject*)':
>> dolfin/swig/dolfin_wrap.cc:76492: warning: 'argv[0]' may be used
>> uninitialized in this function
>> dolfin/swig/dolfin_wrap.cc: In function 'PyObject*
>> _wrap_new_MeshGeometry(PyObject*, PyObject*)':
>> dolfin/swig/dolfin_wrap.cc:75192: warning: 'argv[0]' may be used
>> uninitialized in this function
>> dolfin/swig/dolfin_wrap.cc: In function 'PyObject*
>> _wrap_new_Vector(PyObject*, PyObject*)':
>> dolfin/swig/dolfin_wrap.cc:50862: warning: 'argv[0]' may be used
>> uninitialized in this function
>> dolfin/swig/dolfin_wrap.cc: In function 'PyObject*
>> _wrap_new_uBLASVector(PyObject*, PyObject*)':
>> dolfin/swig/dolfin_wrap.cc:41746: warning: 'argv[0]' may be used
>> uninitialized in this function
>> dolfin/swig/dolfin_wrap.cc: In function 'PyObject*
>> _wrap_new_uBLASILUPreconditioner(PyObject*, PyObject*)':
>> dolfin/swig/dolfin_wrap.cc:50585: warning: 'argv[0]' may be used
>> uninitialized in this function
>> dolfin/swig/dolfin_wrap.cc: In function 'PyObject*
>> _wrap_new_PETScVector(PyObject*, PyObject*)':
>> dolfin/swig/dolfin_wrap.cc:44047: warning: 'argv[0]' may be used
>> uninitialized in this function
>> dolfin/swig/dolfin_wrap.cc: In function 'PyObject*
>> _wrap_new_Table(PyObject*, PyObject*)':
>> dolfin/swig/dolfin_wrap.cc:30960: warning: 'argv[0]' may be used
>> uninitialized in this function
>> dolfin/swig/dolfin_wrap.cc: In function 'PyObject*
>> _wrap_new_Mesh(PyObject*, PyObject*)':
>> dolfin/swig/dolfin_wrap.cc:78823: warning: 'argv[0]' may be used
>> uninitialized in this function
>> mpicxx -o dolfin/swig/_dolfin.so -pthread -Wl,--export-dynamic -shared
>> dolfin/swig/dolfin_wrap.os -Ldolfin
>> -L/usr/lib/petscdir/2.3.3/lib/linux-gnu-c-opt -L/usr/lib/atlas
>> -L/usr/lib/atlas -lxml2 -lpetscts -lpetscsnes -lpetscksp -lpetscdm
>> -lpetscmat -lpetscvec -lpetsc -lblas -lumfpack -lamd -lgts -lm
>> -lgthread-2.0 -lrt -lgmodule-2.0 -ldl -lglib-2.0 -llapack -lblas
>> -lcholmod -lamd -lcolamd -ldolfin
>> scons: done building targets.
>>
>> Thanks,
>> Tim
>> _______________________________________________
>> DOLFIN-dev mailing list
>> DOLFIN-dev@xxxxxxxxxx
>> http://www.fenics.org/mailman/listinfo/dolfin-dev
>
>



-- 
Timothy J. Crone
Lamont-Doherty Earth Observatory
Columbia University
61 Route 9W
Palisades, NY 10964
Tel: 845-365-8687

http://dactyl.ldeo.columbia.edu


Follow ups

References