[issue9191] winreg.c:Reg2Py() may leak memory (in unusual circumstances)

2015-03-07 Thread Claudiu Popa
Claudiu Popa added the comment: This was fixed a couple of months ago: https://hg.python.org/cpython/rev/07968254be96. Also, malloc was changed to PyMem_New a couple of weeks ago: https://hg.python.org/cpython/rev/036a2aceae93 -- nosy: +Claudiu.Popa resolution: - fixed stage: needs

[issue9191] winreg.c:Reg2Py() may leak memory (in unusual circumstances)

2014-06-17 Thread Mark Lawrence
Mark Lawrence added the comment: Can somebody answer the question about PyMem versus malloc/free functions. -- nosy: +BreamoreBoy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9191 ___

[issue9191] winreg.c:Reg2Py() may leak memory (in unusual circumstances)

2014-06-17 Thread Brian Curtin
Changes by Brian Curtin br...@python.org: -- nosy: -brian.curtin ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9191 ___ ___ Python-bugs-list

[issue9191] winreg.c:Reg2Py() may leak memory (in unusual circumstances)

2010-07-07 Thread Daniel Stutzbach
New submission from Daniel Stutzbach dan...@stutzbachenterprises.com: In Reg2Py() in winreg.c, in the REG_MULTI_SZ case, there's the following: wchar_t **str = (wchar_t **)malloc(sizeof(wchar_t *)*s); if (str == NULL) return PyErr_NoMemory();

[issue9191] winreg.c:Reg2Py() may leak memory (in unusual circumstances)

2010-07-07 Thread Brian Curtin
Changes by Brian Curtin cur...@acm.org: -- nosy: +brian.curtin ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9191 ___ ___ Python-bugs-list mailing