[pythran] Re: installation on openSuse -> segfault

  • From: Marc Gailhanou <marc.gailhanou@xxxxxxxx>
  • To: pythran@xxxxxxxxxxxxx
  • Date: Fri, 24 Apr 2015 14:26:09 +0200

Update concerning the tests : on my machine for an unknown reason pip is a symbolic link to pip3.4. Using explicitely pip2.7 I was able to install pytest-pep8 for python 2.7. However the test end up with :

======================================================================== FAILURES ==========================================================================
________________________________________________________________________ PEP8-check _________________________________________________________________________
/usr/local/src/pythran-0.7.0/pythran/backend.py:1085:25: E701 multiple statements on one line (colon)
def op(l, r): return '({0} and {1})'.format(l, r)
/usr/local/src/pythran-0.7.0/pythran/backend.py:1087:25: E701 multiple statements on one line (colon)
def op(l, r): return '({0} or {1})'.format(l, r)

________________________________________________________________________ PEP8-check _________________________________________________________________________
/usr/local/src/pythran-0.7.0/pythran/cxxtypes.py:43:27: E701 multiple statements on one line (colon)
def same(x, y): return getattr(self, x) == getattr(other, y)

============================================================ 2 failed, 88 passed in 7.62 seconds ============================================================


Le 24/04/2015 10:56, Marc Gailhanou a écrit :

Hi Serge,
thanks for you answer

you need to

pip install pytest-pep8

that's only mentionned in the dev guide, and that got fixed in the git
but not in the rlease...

I have done that and still have the same error - because only the python 3 version was installed, and I use python 2.7. Okay I try to solve this by myself.

That's definitively an error. If you're brave enough, you can issue a
pull request on github / send us a patch (so that you'll get the proper
attribution for the fix) or I'll do it.
I am not familiar with those tools and not very brave, I prefer to let you do it ...

Concerning the segfault, I need some more info. If you run your code
under gdb or valgrind, you may get a stacktrace that will help us a lot

gdb --arg python -c 'import dprod; print dprod.dprod([1,2,3], [4,5,6])'

then hit `r'

for easier online debugging, join #pythran on freenode!

From gdb :

Starting program: /usr/bin/python -c import\ dprod\;\ print\ dprod.dprod\(\[1,2,3\],\ \[4,5,6\]\)
Got object file from memory but can't read symbols: Fichier tronqué.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
list (other=..., this=0x7fffff7fef90) at /usr/lib/python2.7/site-packages/pythran/pythonic/types/list.hpp:182
182 list(list<T> const & other) : data(other.data), shape(*this) {}

Freenode : again I do not know anything about this but I will have a look ...

Marc Gailhanou <marc.gailhanou@xxxxxxxx>

Institut Matériaux Microélectronique Nanosciences de Provence ( IM2NP )
UMR 6242 CNRS,
Case 262, Aix Marseille Université ( AMU )
Faculté des Sciences et Techniques de St Jérôme
Av. de l'Escadrille Normandie-Niemen
13397 Marseille Cedex 20

tel 04 9128 8125
fax 04 9128 2793
S'il vous plaît, évitez de m'envoyer des fichiers attachés au
format Word ou PowerPoint, sauf si vous n'avez pas le choix.
Voir http://www.gnu.org/philosophy/no-word-attachments.fr.html

Other related posts: