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

stan mihai added the comment: ok, please also fix the first parameter of the tests. Because it has the same value in the first call and the callback it will always be right by accident, since the first call puts the value in both standard and floating point registers

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

stan mihai added the comment: attached patch with tests I have no experience with python development so the tests will actually need a more detailed review. Also I only checked it on win64. -- Added file: http://bugs.python.org/file20626/ctypes_win64_tests.diff

[issue9266] ctypes "ValueError: NULL pointer access" on Win7 x64

stan mihai added the comment: The problem was an uninitialized variable. Attached is the patch that fixes it. -- keywords: +patch nosy: +stan.mihai Added file: http://bugs.python.org/file20529/ctypes_win64.diff ___ Python tracker <h

[issue9884] The 4th parameter of method always None or 0 on x64 Windows.

stan mihai added the comment: Disabling optimizations doesn't really fix the issue, just hides it, for now. The problem was an uninitialized variable. Attached is the patch that fixes it. -- keywords: +patch nosy: +stan.mihai Added file: http://bugs.python.org/file20528/ctypes_

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

stan mihai added the comment: Disabling optimizations doesn't really fix the issue, just hides it, for now. The problem was an uninitialized variable. Attached is the patch that fixes it. -- nosy: +stan.mihai Added file: http://bugs.python.org/file20527/ctypes_win64