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

2019-02-13 Thread Jeroen Demeyer
Jeroen Demeyer added the comment: See also https://bugs.python.org/issue35983 for another trashcan-related issue. -- nosy: +jdemeyer ___ Python tracker ___

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

2019-01-07 Thread STINNER Victor
STINNER Victor added the comment: This issue is closed. Can you please open a new issue? Try to describe the bug that you have and what you attemped to fix it. -- ___ Python tracker

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

2018-12-24 Thread 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

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

2018-12-24 Thread 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:

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

2017-04-21 Thread STINNER Victor
Changes by STINNER Victor : -- nosy: +haypo ___ Python tracker ___ ___

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

2015-08-13 Thread Antoine Pitrou
Antoine Pitrou added the comment: I'm seeing this bug in Python 3.4.2 as well, and the patch here (tstate_trashcan.patch) appears to fix it. What is the context? Some specific C code? -- ___ Python tracker rep...@bugs.python.org

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

2015-08-12 Thread Larry Hastings
Larry Hastings added the comment: Can anyone else confirm this bug in 3.4? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17703 ___ ___

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

2015-08-12 Thread Stian Lode
Stian Lode added the comment: I'm seeing this bug in Python 3.4.2 as well, and the patch here (tstate_trashcan.patch) appears to fix it. I'm using boost 1.57.0, and Python was compiled on a vanilla rhel6 system. -- nosy: +Stian Lode, larry versions: +Python 3.4 -Python 2.7 Added file:

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

2015-04-18 Thread Daniel
Daniel added the comment: Guillaume already mentioned this, its still causing a Fatal Error. To fix this PyThreadState_GET() in Py_TRASHCAN_SAFE_BEGIN must be replaced with _PyThreadState_Current #define Py_TRASHCAN_SAFE_BEGIN(op) \ do { \ PyThreadState *_tstate =

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

2014-08-01 Thread Guillaume Matte
Guillaume Matte added the comment: It does still cause a Fatal Error in debug build as PyThreadState_GET() error out if _PyThreadState_Current is NULL -- nosy: +flex.plexico ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17703

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

2013-04-15 Thread Antoine Pitrou
Changes by Antoine Pitrou pit...@free.fr: -- title: Trash can mechanism segfault during interpreter finalization in Python 2.7.4 - Trashcan mechanism segfault during interpreter finalization in Python 2.7.4 ___ Python tracker rep...@bugs.python.org

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

2013-04-15 Thread Antoine Pitrou
Changes by Antoine Pitrou pit...@free.fr: -- stage: - commit review type: - crash ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17703 ___ ___

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

2013-04-15 Thread Roundup Robot
Roundup Robot added the comment: New changeset e814fbd470bf by Antoine Pitrou in branch '2.7': Issue #17703: Fix a regression where an illegal use of Py_DECREF() after interpreter finalization can cause a crash. http://hg.python.org/cpython/rev/e814fbd470bf -- nosy: +python-dev

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

2013-04-15 Thread Antoine Pitrou
Antoine Pitrou added the comment: Committed! -- resolution: - fixed stage: commit review - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17703 ___

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

2013-04-15 Thread Marc-Andre Lemburg
Marc-Andre Lemburg added the comment: On 15.04.2013 21:21, Antoine Pitrou wrote: Committed! Cool, thanks for the quick turnaround. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17703