This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author JohnLeitch
Recipients BreamoreBoy, JohnLeitch, belopolsky, brycedarling, lemburg, paul.moore, steve.dower, tim.golden, vstinner, zach.ware
Date 2015-09-04.23:47:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1441410442.47.0.458474996561.issue24917@psf.upfronthosting.co.za>
In-reply-to
Content
It very well may apply to versions apart from 3.5. Our test environment is quite complex and unfriendly to working with multiple versions of Python. Plus, we're strapped for time, so we tend to file under the version we're currently targeting and defer to those better equipped and more familiar with the codebase.

The repro file is fine and there's no need to rebuild anything; the heap verification I'm suggesting is applied to binaries, not source. You can find information here:

https://msdn.microsoft.com/en-us/library/windows/hardware/ff549557(v=vs.85).aspx

Install the debugging tools, run GFlags, select the python.exe/pythonw.exe image file, and apply the settings I mentioned in my previous post.
History
Date User Action Args
2015-09-04 23:47:22JohnLeitchsetrecipients: + JohnLeitch, lemburg, paul.moore, belopolsky, vstinner, tim.golden, BreamoreBoy, zach.ware, steve.dower, brycedarling
2015-09-04 23:47:22JohnLeitchsetmessageid: <1441410442.47.0.458474996561.issue24917@psf.upfronthosting.co.za>
2015-09-04 23:47:22JohnLeitchlinkissue24917 messages
2015-09-04 23:47:21JohnLeitchcreate