[issue30640] NULL + 1 in _PyFunction_FastCallDict(), PyEval_EvalCodeEx()

2017-09-07 Thread STINNER Victor
STINNER Victor added the comment: It's now fixed in Python 3.6 and master (3.7). FYI this issue was also detected by Coverity as CID 1415964. -- resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker

[issue30640] NULL + 1 in _PyFunction_FastCallDict(), PyEval_EvalCodeEx()

2017-09-07 Thread STINNER Victor
STINNER Victor added the comment: New changeset f032e9237aa7d43d21e0b04d685c36bddf7078c1 by Victor Stinner (Zackery Spytz) in branch '3.6': [3.6] bpo-30640: Fix undefined behavior in _PyFunction_FastCallDict() and PyEval_EvalCodeEx() (GH-2919) (#2964)

[issue30640] NULL + 1 in _PyFunction_FastCallDict(), PyEval_EvalCodeEx()

2017-07-31 Thread Zackery Spytz
Changes by Zackery Spytz : -- pull_requests: +3011 ___ Python tracker ___ ___

[issue30640] NULL + 1 in _PyFunction_FastCallDict(), PyEval_EvalCodeEx()

2017-07-31 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: New changeset c6ea8974e2d939223bfd6d64ee13ec89c090d2e0 by Serhiy Storchaka (Zackery Spytz) in branch 'master': bpo-30640: Fix undefined behavior in _PyFunction_FastCallDict() and PyEval_EvalCodeEx() (#2919)

[issue30640] NULL + 1 in _PyFunction_FastCallDict(), PyEval_EvalCodeEx()

2017-07-30 Thread Zackery Spytz
Zackery Spytz added the comment: As mentioned in PR 2919, this is an issue in PyEval_EvalCodeEx() as well. -- nosy: +ZackerySpytz title: NULL + 1 in _PyFunction_FastCallDict() -> NULL + 1 in _PyFunction_FastCallDict(), PyEval_EvalCodeEx() ___ Python