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 fijal
Recipients christian.heimes, facundobatista, fijal, georg.brandl, gvanrossum, schmir
Date 2008-01-22.11:29:04
SpamBayes Score 0.015913263
Marked as misclassified No
Message-id <4795D37E.5010201@genesilico.pl>
In-reply-to <4795D172.7070709@cheimes.de>
Content
PyPy is all MIT, no problem at license. This should not be plugged into 
the parser, this is not a patch (especially not a patch for the parser). 
This file is rather to illustrate possible solution to solve the problem 
of sys.setrecursionlimit not being a robust solution, but just a quick 
hack. Instead of having a counter (which is sometimes too big, sometimes 
too small, depending on amount of C code in between the stack checks), 
it provides a way of measuring the size of a stack actually used. The 
idea is to store the address of local variable somewhere in the 
beginning and compare it to addresses of local variables in consecutive 
calls to LL_stack_too_big (all stored per-thread). This seems to be a 
better solution (ie pypy does not segfault on any of Lib/test/crashers, 
particularly not on ones involving unevident C infinite loop). Yes, it 
has some performance penalty (hard to tell exactly what without trying).

Hum, this indeed might be not a best place to have such discussion, what 
about moving this to another, more general issue?

Cheers,
fijal

:.
History
Date User Action Args
2008-01-22 11:29:14fijalsetspambayes_score: 0.0159133 -> 0.015913263
recipients: + fijal, gvanrossum, georg.brandl, facundobatista, christian.heimes, schmir
2008-01-22 11:29:05fijallinkissue1881 messages
2008-01-22 11:29:04fijalcreate