[issue8275] callback function on win64 results in bad behavior. mem corruption?

Jasmit added the comment: I was able to fix the issue by modifying and re-compiling ctypes project in Visual Studio 2008. The following properties were modified: Release: configuration Properties->C/C++->Optimization->Optimization: Disabled(/Od) configuration Properties->C/C++-&

[issue8275] callback function on win64 results in bad behavior. mem corruption?

Changes by Jasmit : -- title: callback function on win64 results in bad behavior. mem leak? -> callback function on win64 results in bad behavior. mem corruption? ___ Python tracker <http://bugs.python.org/iss

[issue8275] callback function on win64 results in bad behavior. mem leak?

New submission from Jasmit : I am testing a wrapper on Windows 64 and it seems to result in an null pointer access error ONLY when I insert a print statement in the C code. I have tested the wrapper with Python 2.6 and Python 2.7a4. In addition, I have compiled Python 2.6.5 source code and