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

Antoine Pitrou added the comment: Ok, committed in r88284 (3.2), r88285 (3.1) and r88286 (2.7). Thank you! -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed ___ Python tracker

[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?

Antoine Pitrou added the comment: Patch verified to work under Linux and win32. It looks good, except for tab characters in the Modules/_ctypes/_ctypes_test.c (indentation of C files should use 4 spaces); that's a detail that we can fix ourselves. -- assignee: theller -> ___

[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 __

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

Christoph Gohlke added the comment: Thank you. The new patch works and it also fixes a crash of the python-2.5.4.amd64 interpreter at startup when ctypes 1.0.2 and pyreadline 1.6.2 are installed. -- ___ Python tracker

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

Antoine Pitrou added the comment: Would it be possible to add a test case to the patch? -- nosy: +georg.brandl, pitrou stage: -> patch review type: behavior -> crash versions: +Python 3.1, Python 3.2 -Python 2.6 ___ Python tracker

[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.diff _

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

Christoph Gohlke added the comment: This patch fixes issue #9884 and possibly #9266. -- ___ Python tracker ___ ___ Python-bugs-list ma

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

Changes by Christoph Gohlke : -- nosy: +cgohlke ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

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

Sridhar Ratnakumar added the comment: Attaching a patch for the configuration changes mentioned in msg102544 -- keywords: +patch nosy: +srid Added file: http://bugs.python.org/file20134/issue8275_win64_ctypes_no_optimization.patch ___ Python tracker

[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++->Optimization->

[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