Hi, On 11/08/2012 03:36 PM, Padraig wrote: > Hi > the trace is below. I am running Python 2.7.3 and Boost 1.49. Yes it looks > to same problem indeed. > Padraig > > $ gdb python > GNU gdb (GDB) 7.5-ubuntu > Copyright (C) 2012 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or later > <http://gnu.org/licenses/gpl.html> > This is free software: you are free to change and redistribute it. > There is NO WARRANTY, to the extent permitted by law. Type "show copying" > and "show warranty" for details. > This GDB was configured as "x86_64-linux-gnu". > For bug reporting instructions, please see: > <http://www.gnu.org/software/gdb/bugs/>... > Reading symbols from /usr/bin/python...(no debugging symbols found)...done. > (gdb) run test.py > Starting program: /usr/bin/python test.py > [Thread debugging using libthread_db enabled] > Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". > > Program received signal SIGSEGV, Segmentation fault. > 0x00000000004b5d5a in ?? () > (gdb) bt > #0 0x00000000004b5d5a in ?? () > #1 0x00000000004ef748 in ?? () > #2 0x000000000048a57e in ?? () > #3 0x00007ffff6f1f901 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 > #4 0x00007ffff6f1f985 in exit () from /lib/x86_64-linux-gnu/libc.so.6 > #5 0x00007ffff6f05774 in __libc_start_main () > from /lib/x86_64-linux-gnu/libc.so.6 > #6 0x00000000004ce0ad in _start ()
Did you compile it yourself, or you used the ubuntu package? If you compiled it, what GCC did you use? I'm inclined to think this is a problem with openmp (GCC) + boost python. Since I cannot reproduce this problem, I cannot investigate myself. I would suggest different versions of GCC and Boost, and see if the problem also happens there. -- Tiago de Paula Peixoto <[email protected]>
signature.asc
Description: OpenPGP digital signature
_______________________________________________ graph-tool mailing list [email protected] http://lists.skewed.de/mailman/listinfo/graph-tool
