Stop using PyMem_FREE while the GIL is not held. For details see:

http://mail.python.org/pipermail/python-dev/2007-May/072896.html
This commit is contained in:
Neal Norwitz 2007-05-02 04:47:55 +00:00
parent c0a293c692
commit d83eb316dc
2 changed files with 3 additions and 1 deletions

View File

@ -30,6 +30,8 @@ extern "C" {
debugging info to dynamic memory blocks. The system routines have no idea
what to do with that stuff, and the Python wrappers have no idea what to do
with raw blocks obtained directly by the system routines then.
The GIL must be held when using these APIs.
*/
/*

View File

@ -6296,8 +6296,8 @@ posix_fdopen(PyObject *self, PyObject *args)
#else
fp = fdopen(fd, mode);
#endif
PyMem_FREE(mode);
Py_END_ALLOW_THREADS
PyMem_FREE(mode);
if (fp == NULL)
return posix_error();
f = PyFile_FromFile(fp, "<fdopen>", orgmode, fclose);