Re: Python deadlock using subprocess.popen and communicate



On Fri, 23 Sep 2011 06:59:12 +0100, Nobody wrote:

kernel32.dll!WaitForSingleObject+0x12
python26.dll!_Py_svnversion+0xcf8

I haven't a clue how this happens. _Py_svnversion just returns a string:

In retrospect, I think that's a red herring. 0xcf8 seems like too large an
offset for such a small function. I think that it's more likely to be in a
non-exported function, and _Py_svnversion just happens to be the last
exported symbol prior to that point in the code.

.