[issue3299] Direct calls to PyObject_Del/PyObject_DEL are broken for --with-pydebug

STINNER Victor added the comment: > I will open new issues for the two remaining patches. Done: #9402 for pyexpat and #9403 for cElementTree. -- resolution: -> fixed status: open -> closed ___ Python tracker

[issue3299] Direct calls to PyObject_Del/PyObject_DEL are broken for --with-pydebug

STINNER Victor added the comment: I will open new issues for the two remaining patches. -- ___ Python tracker ___ ___ Python-bugs-list

[issue3299] Direct calls to PyObject_Del/PyObject_DEL are broken for --with-pydebug

Nick Coghlan added the comment: I believe the two attached patches still need to be checked. -- ___ Python tracker ___ ___ Python-bugs

[issue3299] Direct calls to PyObject_Del/PyObject_DEL are broken for --with-pydebug

Mark Lawrence added the comment: Loads of comments about backports, can this be closed or are there still any outstanding issues? -- nosy: +BreamoreBoy ___ Python tracker ___ __

[issue3299] Direct calls to PyObject_Del/PyObject_DEL are broken for --with-pydebug

Changes by STINNER Victor : Removed file: http://bugs.python.org/file15880/_curses_panel_py_decref.patch ___ Python tracker ___ ___ Python-bugs

[issue3299] Direct calls to PyObject_Del/PyObject_DEL are broken for --with-pydebug

Changes by STINNER Victor : Removed file: http://bugs.python.org/file15863/thread_py_decref.patch ___ Python tracker ___ ___ Python-bugs-list m

[issue3299] Direct calls to PyObject_Del/PyObject_DEL are broken for --with-pydebug

STINNER Victor added the comment: > thread fix commited: r78610 (trunk) > curses panel fix commited: r78635 (trunk) Backport done in r79198 (2.6). -- ___ Python tracker ___

[issue3299] Direct calls to PyObject_Del/PyObject_DEL are broken for --with-pydebug

STINNER Victor added the comment: thread fix commited: r78610 (trunk), r78611 (py3k), r78612 (3.1). Delay the backport to 2.6 after the 2.6.5 release. -- ___ Python tracker ___

[issue3299] Direct calls to PyObject_Del/PyObject_DEL are broken for --with-pydebug

Changes by STINNER Victor : Removed file: http://bugs.python.org/file10893/pyobject_del.patch ___ Python tracker ___ ___ Python-bugs-list maili

[issue3299] Direct calls to PyObject_Del/PyObject_DEL are broken for --with-pydebug

STINNER Victor added the comment: Patch for cElementTree: * Replace PyObject_Del() by Py_DECREF() * Catch element_new_extra() errors * parser dealloc: replace Py_DECREF() by Py_XDECREF() because the pointer may be NULL (error in the constructor) * set all parser attributes to NULL at the be

[issue3299] Direct calls to PyObject_Del/PyObject_DEL are broken for --with-pydebug

STINNER Victor added the comment: Update pyexpat patch. As _curses_panel, the bug is raised on malloc() failure. The patch adds also a dummy test on ExternalEntityParserCreate(). -- Added file: http://bugs.python.org/file15881/pyexpat_py_decref.patch __

[issue3299] Direct calls to PyObject_Del/PyObject_DEL are broken for --with-pydebug

Changes by STINNER Victor : Removed file: http://bugs.python.org/file10892/_curses_panel.patch ___ Python tracker ___ ___ Python-bugs-list mail

[issue3299] Direct calls to PyObject_Del/PyObject_DEL are broken for --with-pydebug

Antoine Pitrou added the comment: > I don't know how to write reliable test for this case. Maybe using > http://www.nongnu.org/failmalloc/ library (a little bit overkill, isn't > > it?). Yes, it would IMO be overkill. -- ___ Python tracker

[issue3299] Direct calls to PyObject_Del/PyObject_DEL are broken for --with-pydebug

Changes by Antoine Pitrou : Removed file: http://bugs.python.org/file15878/sre_py_decref-2.patch ___ Python tracker ___ ___ Python-bugs-list ma

[issue3299] Direct calls to PyObject_Del/PyObject_DEL are broken for --with-pydebug

Antoine Pitrou added the comment: The sre patch has been committed, thank you! -- ___ Python tracker ___ ___ Python-bugs-list mailing

[issue3299] Direct calls to PyObject_Del/PyObject_DEL are broken for --with-pydebug

STINNER Victor added the comment: Update _curses_panel patch. The crash occurs if malloc() fail in insert_lop(). I don't know how to write reliable test for this case. Maybe using http://www.nongnu.org/failmalloc/ library (a little bit overkill, isn't it?). -- ___

[issue3299] Direct calls to PyObject_Del/PyObject_DEL are broken for --with-pydebug

Changes by STINNER Victor : Added file: http://bugs.python.org/file15880/_curses_panel_py_decref.patch ___ Python tracker ___ ___ Python-bugs-l

[issue3299] Direct calls to PyObject_Del/PyObject_DEL are broken for --with-pydebug

Changes by STINNER Victor : Removed file: http://bugs.python.org/file15862/sre_py_decref.patch ___ Python tracker ___ ___ Python-bugs-list mail

[issue3299] Direct calls to PyObject_Del/PyObject_DEL are broken for --with-pydebug

Changes by STINNER Victor : Removed file: http://bugs.python.org/file10891/_sre-2.patch ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue3299] Direct calls to PyObject_Del/PyObject_DEL are broken for --with-pydebug

STINNER Victor added the comment: > Victor, your overflow test in the sre patch tests for TypeError, > but OverflowError is actually raised: (...) Oops, fixed. -- Added file: http://bugs.python.org/file15878/sre_py_decref-2.patch ___ Python tracker

[issue3299] Direct calls to PyObject_Del/PyObject_DEL are broken for --with-pydebug

Antoine Pitrou added the comment: Victor, your overflow test in the sre patch tests for TypeError, but OverflowError is actually raised: == ERROR: test_dealloc (test.test_re.ReTests) ---

[issue3299] Direct calls to PyObject_Del/PyObject_DEL are broken for --with-pydebug

Changes by Antoine Pitrou : -- nosy: +pitrou stage: -> patch review versions: +Python 3.2 -Python 3.0 ___ Python tracker ___ ___ Pytho

[issue3299] Direct calls to PyObject_Del/PyObject_DEL are broken for --with-pydebug

STINNER Victor added the comment: This issue is still open, it's still possible to crash Python in debug mode. I updated patches for the _sre and thread modules. -- ___ Python tracker _

[issue3299] Direct calls to PyObject_Del/PyObject_DEL are broken for --with-pydebug

Changes by STINNER Victor : Added file: http://bugs.python.org/file15863/thread_py_decref.patch ___ Python tracker ___ ___ Python-bugs-list mai

[issue3299] Direct calls to PyObject_Del/PyObject_DEL are broken for --with-pydebug

Changes by STINNER Victor : Added file: http://bugs.python.org/file15862/sre_py_decref.patch ___ Python tracker ___ ___ Python-bugs-list mailin

[issue3299] Direct calls to PyObject_Del/PyObject_DEL are broken for --with-pydebug

Nick Coghlan added the comment: Ah, now that I go to implement it, I remember why I didn't like the idea of doing anything directly in PyObject_Del. While the Python memory allocator is primarily designed for allocation of Python objects, it isn't actually *limited* to that. So there is no guara

[issue3299] Direct calls to PyObject_Del/PyObject_DEL are broken for --with-pydebug

Nick Coghlan added the comment: (changing title and unassigning from Fredrik since this isn't an RE specific problem, flagged as also affecting interpreter core, flagged as affecting all currently maintained versions) -- assignee: effbot -> components: +Interpreter Core title: invalid