[issue14239] Uninitialised variable in _PyObject_GenericSetAttrWithDict

2012-03-09 Thread Jim Jewett
Jim Jewett added the comment: So the risk is that descr may be given garbage memory that just happens to look like an object with 1 reference, so that it really does a decref and tries to re-deallocate whatever was there before. I would rather see the change at the top of the function; just i

[issue14239] Uninitialised variable in _PyObject_GenericSetAttrWithDict

2012-03-09 Thread Benjamin Peterson
Benjamin Peterson added the comment: Fixed in differently in 46e600fa8d05 Thanks anyway. -- resolution: -> out of date status: open -> closed ___ Python tracker ___ ___

[issue14239] Uninitialised variable in _PyObject_GenericSetAttrWithDict

2012-03-09 Thread Antoine Pitrou
Changes by Antoine Pitrou : -- nosy: +benjamin.peterson ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://

[issue14239] Uninitialised variable in _PyObject_GenericSetAttrWithDict

2012-03-09 Thread Mark Shannon
New submission from Mark Shannon : I get the following compiler warning (rev 2a142141e5fd) Its not strictly an error, but an unitialised variable in such an important function is dangerous. Objects/object.c: In function ‘_PyObject_GenericSetAttrWithDict’: Objects/object.c:1144: warning: ‘descr’