Author Mark.Shannon
Recipients Arfrever, Mark.Shannon, amaury.forgeotdarc, asvetlov, benjamin.peterson, brett.cannon, dmalcolm, ilblackdragon, jcea, jkloth, larry, lemburg, mark.dickinson, python-dev, vstinner
Date 2013-06-25.19:15:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1372187741.43.0.999000805487.issue17206@psf.upfronthosting.co.za>
In-reply-to
Content
I think blaming the crash in test_marshall
http://buildbot.python.org/all/builders/AMD64%20Windows7%20SP1%203.x/builds/2009/steps/test/logs/stdio
on the new macros (change aff41a6421c2) is correct.

It may be the proximate cause, but that doesn't make it the underlying one. The interpreter should be more resilient against minor changes to the amount of C stack used per call.

Can we get a full stack trace (for the C stack not the Python one) for the failure?
History
Date User Action Args
2013-06-25 19:15:41Mark.Shannonsetrecipients: + Mark.Shannon, lemburg, brett.cannon, jcea, amaury.forgeotdarc, mark.dickinson, vstinner, larry, benjamin.peterson, jkloth, Arfrever, asvetlov, dmalcolm, python-dev, ilblackdragon
2013-06-25 19:15:41Mark.Shannonsetmessageid: <1372187741.43.0.999000805487.issue17206@psf.upfronthosting.co.za>
2013-06-25 19:15:41Mark.Shannonlinkissue17206 messages
2013-06-25 19:15:41Mark.Shannoncreate