Re: module_traverse segfault

2014-06-16 Thread Terry Reedy
On 6/16/2014 4:16 PM, Roland Plüss wrote: Was the program supposed to be shutting down when this occurred? Or did this happen during 'normal' execution? Shutting down. It happens though also if I trigger an error for example using if( ! PyArg_ParseTuple( args, "", &x1, &y1, &x2, &y2 )

Re: module_traverse segfault

2014-06-16 Thread Roland Plüss
>> Program received signal SIGSEGV, Segmentation fault. >> 0x7fffc958 in ?? () >> (gdb) bt >> #0 0x7fffc958 in ?? () >> #1 0x7fffdd2f9ed0 in module_traverse () from >> /usr/lib64/libpython3.3.so.1.0 >> #2 0x7fffdd396cc7 in collect_with_callback () from >> /usr/lib64/libp

Re: module_traverse segfault

2014-06-16 Thread Terry Reedy
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. 0x7fffc958 in ?? () (gdb) bt #0 0x7f