On 6/16/2014 1:14 PM, Roland Plüss wrote:
I'm still trying to get Python3 embedded working. The main problem I'm
hitting now is an unexplainable segfault:


/unexplainable/unexplained/ ;-)

Program received signal SIGSEGV, Segmentation fault.
0x00007fffffffc958 in ?? ()
(gdb) bt
#0  0x00007fffffffc958 in ?? ()
#1  0x00007fffdd2f9ed0 in module_traverse () from
/usr/lib64/libpython3.3.so.1.0
#2  0x00007fffdd396cc7 in collect_with_callback () from
/usr/lib64/libpython3.3.so.1.0
#3  0x00007fffdd397738 in PyGC_Collect () from
/usr/lib64/libpython3.3.so.1.0
#4  0x00007fffdd3808ca in Py_Finalize () from /usr/lib64/libpython3.3.so.1.0

Can you run (some of) the same code in a normal interpreter? If so, does it raise an uncaught exception?

Was the program supposed to be shutting down when this occurred? Or did this happen during 'normal' execution?

In any case, switch to 3.4.1 or later for improved gc and finalization.

--
Terry Jan Reedy


--
https://mail.python.org/mailman/listinfo/python-list

Reply via email to