Johnny Lee added the comment:
> It's difficult to really test such errors.
When I can't control the called function, I usually step through the
code in a debugger and change the result variable in question to the
appropriate value to see if the code handles failed function cal
Johnny Lee added the comment:
attached modified diff patch so line length <=79 chars
Added file: http://bugs.python.org/file12374/py30dif2.txt
___
Python tracker
<http://bugs.python.org/iss
Changes by Johnny Lee :
Removed file: http://bugs.python.org/file12335/py30diff.txt
___
Python tracker
<http://bugs.python.org/issue4653>
___
___
Python-bugs-list mailin
Johnny Lee added the comment:
For the dynload_win.c typo, it's technically a possible buffer
overflow, but you'd need to find an error that had an error message
that's longer than 259 chars.
In pythonrun.c, the if statements for fout and ferr and almost
identical. Probably
Johnny Lee added the comment:
Here are the URLs to the MSDN documentation for CreateFileMapping and
FormatMessage[A|W]:
<http://msdn.microsoft.com/en-us/library/aa366537.aspx>
<http://msdn.microsoft.com/en-us/library/ms679351.aspx>
For CreateFileMapping(), from the Return Value
New submission from Johnny Lee :
I ran my typo.pl perl script that locates possible C/C++ typos.
I found four that looked valid.
Two of the typos were in the Python directory {pythonrun.c,
dynload_win.c}, two were in PC/bdist_wininst {install.c, extract.c}.
Python/dynload_win.c:
Win32 API
