[issue17187] Python segfaults from improperly formed and called function

Changes by Benjamin Peterson : -- resolution: -> not a bug stage: needs patch -> resolved status: pending -> closed ___ Python tracker

[issue17187] Python segfaults from improperly formed and called function

Serhiy Storchaka added the comment: I suggest to close this issue as "not a bug" or "wont fix". -- nosy: +serhiy.storchaka status: open -> pending ___ Python tracker

[issue17187] Python segfaults from improperly formed and called function

Changes by Terry J. Reedy tjre...@udel.edu: -- nosy: +terry.reedy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17187 ___ ___ Python-bugs-list

[issue17187] Python segfaults from improperly formed and called function

Ramchandra Apte added the comment: Perhaps types.CodeType should refuse to generate the malformed code object in the first place? Yup. -- nosy: +ramchandra.apte ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17187

[issue17187] Python segfaults from improperly formed and called function

Benjamin Peterson added the comment: In general, you can generate whatever junky bytecode you want, and the eval loop will happy crash itself. Your on your own when screwing with types.CodeType. -- nosy: +benjamin.peterson ___ Python tracker

[issue17187] Python segfaults from improperly formed and called function

New submission from Larry Hastings: Python 3.3 added a nice new feature: if you don't supply enough positional parameters to a function, it tells you the names of the positional parameters you omitted. Unfortunately, the code that prints this error message assumes that the function is

[issue17187] Python segfaults from improperly formed and called function

Changes by Larry Hastings la...@hastings.org: -- keywords: +patch Added file: http://bugs.python.org/file29044/lch.bandaid.for.malformed.fn.crash.1.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17187