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 mhammond
Recipients mhammond, pitrou
Date 2008-08-21.23:21:40
SpamBayes Score 3.8636227e-07
Marked as misclassified No
Message-id <1219360903.53.0.323822932018.issue3640@psf.upfronthosting.co.za>
In-reply-to
Content
[from python-dev]
I've found a recursion related crash in test_cpickle on 64bit builds. 
Specifically, the 'cPickleDeepRecursive' is causing a stack overflow,
and the debugger tells me the actual recursion depth was 629 at the crash.

The reason the 64bit build doesn't see more crashes is apparently due to
another regression in 2.6 - http://bugs.python.org/issue3373.  It
appears that in some cases, the recursion counter is actually
incremented *twice* for each entry, thereby causing the "maximum
recursion depth exceeded" exception to appear at a true recursion limit
of 500.  However, test_cpickle takes a different path and doesn't see
this doubling of the count - therefore dieing at the depth of 629 that I
can see.

My solution to this was to simply double the stack size for the
executables in 64bit builds, from 2MB to 4MB (2.1 and 4.2 for debug
builds.)  Is this an appropriate fix?
History
Date User Action Args
2008-08-21 23:21:43mhammondsetrecipients: + mhammond, pitrou
2008-08-21 23:21:43mhammondsetmessageid: <1219360903.53.0.323822932018.issue3640@psf.upfronthosting.co.za>
2008-08-21 23:21:41mhammondlinkissue3640 messages
2008-08-21 23:21:40mhammondcreate