[issue5392] stack overflow after hitting recursion limit twice

Changes by Antoine Pitrou : -- status: pending -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://

[issue5392] stack overflow after hitting recursion limit twice

Antoine Pitrou added the comment: Committed in r70344. -- resolution: -> fixed status: open -> pending ___ Python tracker ___ ___ Pyt

[issue5392] stack overflow after hitting recursion limit twice

Martin v. Löwis added the comment: > The fact it fails only the second time is by design, although I'm not > sure the design is useful, and it's probably not documented anywhere. It helped me debug a number of interpreter crashes in 3.0. When a stack overflow occurred, in certain cases, the int

[issue5392] stack overflow after hitting recursion limit twice

Antoine Pitrou added the comment: Here is a patch. I've put the tests in test_sys.py, I haven't found a better place for them. -- keywords: +patch Added file: http://bugs.python.org/file13218/issue5392.patch ___ Python tracker

[issue5392] stack overflow after hitting recursion limit twice

Changes by Antoine Pitrou : -- assignee: -> pitrou priority: -> normal ___ Python tracker ___ ___ Python-bugs-list mailing list Unsub

[issue5392] stack overflow after hitting recursion limit twice

Antoine Pitrou added the comment: The fact it fails only the second time is by design, although I'm not sure the design is useful, and it's probably not documented anywhere. The error message says it : "Cannot *recover* from stack overflow", which means there was a first stack overflow, and Pyth

[issue5392] stack overflow after hitting recursion limit twice

Gabriel Genellina added the comment: It is an artificial value, I don't require a recursion limit so low in any application. I found it when looking into #5370. If there is a lower limit to sys.setrecursionlimit, maybe it should be enforced. But since it fails only the second time, it looks

[issue5392] stack overflow after hitting recursion limit twice

Antoine Pitrou added the comment: This is probably due to the recursion overflow recovery code in py3k, which has a hard-wired constant of 50 somewhere :-) (is setting the recursion limit so low a requirement for your application? or were you just experimenting with it? as Georg said, it's not

[issue5392] stack overflow after hitting recursion limit twice

Georg Brandl added the comment: I can reproduce that (with the same limits) on Linux here. It doesn't happen with 2.6. (Although it is technically not a crash but a controlled abort().) -- nosy: +georg.brandl ___ Python tracker

[issue5392] stack overflow after hitting recursion limit twice

Changes by Benjamin Peterson : -- nosy: +loewis, pitrou ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://m

[issue5392] stack overflow after hitting recursion limit twice

New submission from Gabriel Genellina : Set sys.setrecursionlimit to 50 or lower. Then, the second time the recursion limit is reached, the interpreter crashes with a stack overflow. This happens both with released 3.0.1 and the py3k branch, on Windows. At least on my PC, 51 appears to be the m