Message 61382 - Python tracker

➜

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	schmir
Recipients	barry, gvanrossum, jhylton, loewis, schmir
Date	2008-01-21.10:16:59
SpamBayes Score	0.022929769
Marked as misclassified	No
Message-id	<1200910620.7.0.936115382967.issue215555@psf.upfronthosting.co.za>
In-reply-to

Content
Ok, I've upped the limit to some very high value and tried to provoke a stack overflow. eval("["x+"]"x) segfaults on my machine for x somewhere around 20000 (linux, amd64). When setting MAXSTACK to 5000 eval("["x+"]"x) works for x <= 333. So, I guess this should be safe guess (even for the BSDs, which have a smaller default stack size). BTW: The hardest part was recognizing that nothing gets rebuilt and that more then parser.o depended on parser.h. Don't you have some kind of automatic dependency tracking? Or am I missing some build tools? Anyway, patch in http://bugs.python.org/issue1881

Ok, I've upped the limit to some very high value and tried to provoke a
stack overflow.
eval("["*x+"]"*x) segfaults on my machine for x somewhere around 20000
(linux, amd64). When setting MAXSTACK to 5000 eval("["*x+"]"*x) works
for x <= 333. So, I guess this should be safe guess (even for the BSDs,
which have a smaller default stack size).

BTW: The hardest part was recognizing that nothing gets rebuilt and that
more then parser.o depended on parser.h. Don't you have some kind of
automatic dependency tracking? Or am I missing some build tools?

Anyway, patch in http://bugs.python.org/issue1881

History
Date	User	Action	Args
2008-01-21 10:17:00	schmir	set	spambayes_score: 0.0229298 -> 0.022929769 recipients: + schmir, gvanrossum, loewis, jhylton, barry
2008-01-21 10:17:00	schmir	set	spambayes_score: 0.0229298 -> 0.0229298 messageid: <1200910620.7.0.936115382967.issue215555@psf.upfronthosting.co.za>
2008-01-21 10:16:59	schmir	link	issue215555 messages
2008-01-21 10:16:59	schmir	create