Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #73323 > unrolled thread

Re: module_traverse segfault

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: module_traverse segfault Terry Reedy <tjreedy@udel.edu> - 2014-06-16 15:01 -0400

#73323 — Re: module_traverse segfault

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

[toc] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web