➜

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 pitrou
Recipients amaury.forgeotdarc, mmokrejs, neologix, pitrou, sjt, skrah, tim.peters, vstinner
Date 2013-08-31.13:34:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1377956079.86.0.145797767033.issue18843@psf.upfronthosting.co.za>
In-reply-to
Content 
Hardware failures or glitches can involve any number of parameters.
Instead of trying to reproduce the memory corruption with other Python programs, I would suggest you run the exact same workload (including Python version and build options) on another computer (preferably with different hardware characteristics) and see if you can still trigger it.

(bonus points if you can try on a setup with ECC RAM)
History
Date User Action Args
2013-08-31 13:34:39pitrousetrecipients: + pitrou, tim.peters, amaury.forgeotdarc, mmokrejs, vstinner, sjt, skrah, neologix
2013-08-31 13:34:39pitrousetmessageid: <1377956079.86.0.145797767033.issue18843@psf.upfronthosting.co.za>
2013-08-31 13:34:39pitroulinkissue18843 messages
2013-08-31 13:34:39pitroucreate