[issue18287] PyType_Ready() should sanity-check the tp_name field

2013-07-19 Thread Niklas Koep
Changes by Niklas Koep : Removed file: http://bugs.python.org/file30678/patch ___ Python tracker <http://bugs.python.org/issue18287> ___ ___ Python-bugs-list mailin

[issue18287] PyType_Ready() should sanity-check the tp_name field

2013-06-28 Thread Niklas Koep
Niklas Koep added the comment: Oh, you're right, of course. I completely forgot that any other case which jumps to the error label assumes an appropriate exception has already been set. I attached a new patch which raises a TypeError. Is there a better way to identify the type whi

[issue18287] PyType_Ready() should sanity-check the tp_name field

2013-06-23 Thread Niklas Koep
New submission from Niklas Koep: I noticed that defining a new type where the tp_name field is NULL causes segfaults, for instance, when calling pydoc on the extension module. This particular segfault traces back to type_module() in Objects/typeobject.c where tp_name is passed to strrchr