[issue17703] Trashcan mechanism segfault during interpreter finalization in Python 2.7.4

[Trevor Joynson]

Trevor Joynson  added the comment:

I can verify this bug does still in fact exist in all 3.x versions I've tested 
(3.4-3.7).

It's been the cause of many long-standing segfaults we've been having at exit 
in applications that use OpenRAVE and/or boost::python::numeric.

--
nosy: +ned.deily, trevorj
versions: +Python 3.6 -Python 3.4

___
Python tracker 
<https://bugs.python.org/issue17703>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue17703] Trashcan mechanism segfault during interpreter finalization in Python 2.7.4

[Trevor Joynson]

Trevor Joynson  added the comment:

I can also confirm that the included patch does "workaround" the issue.

A big pain point here for me is in determining what exit handler is causing 
this.

GDB has been it's usual great help in determining information about the exact 
segfault, but the problem code itself is rather elusive since it's ran so much 
earlier and just causes this issue downstream later in execution. Unfortunately 
the extensions I'm dealing with also happen to take a lifetime to compile, 
exacerbated by the fact that they are dependent upon one another.

Can we please apply this to 3.x's tree?

--

___
Python tracker 
<https://bugs.python.org/issue17703>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com