[issue34192] FunctionType.__new__ can generate functions that immediately crash

Dennis Sweeney added the comment: >From >https://github.com/python/cpython/blob/main/Lib/test/crashers/bogus_code_obj.py > : """ Broken bytecode objects can easily crash the interpreter. This is not going to be fixed. It is generally agreed that there is no point in writing a bytecode

[issue34192] FunctionType.__new__ can generate functions that immediately crash

Karthikeyan Singaravelan added the comment: The assertion also fails on master. I did some manual git blame work. The assertion passes with commit 7324b5ce8e7c031a0a3832a6a8d7c639111ae0ff. It fails with the next commit 078f1814f1a4413a2a0fdb8cf4490ee0fc98ef34

[issue34192] FunctionType.__new__ can generate functions that immediately crash

Change by Karthikeyan Singaravelan : -- nosy: +xtreak ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34192] FunctionType.__new__ can generate functions that immediately crash

Change by Raymond Hettinger : -- nosy: +rhettinger ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue34192] FunctionType.__new__ can generate functions that immediately crash

New submission from Dan Snider : The following program crashes on 3.3.1, 3.4.2, 3.5.2, and 3.6.1 because despite having a non-empty co_cellvars slot due to the generator object, the NOFREE flag was set. 3.7 isn't immune to some bad behavior here, either. While I only have access to 3.7.03b