From 658fad8aae60e6c25a102fb56884bf66577366f8 Mon Sep 17 00:00:00 2001 From: Antoine Pitrou Date: Wed, 3 Sep 2008 18:34:34 +0000 Subject: Issue #3697: "Fatal Python error: Cannot recover from stack overflow" could be easily encountered under Windows in debug mode when exercising the recursion limit checking code, due to bogus handling of recursion limit when USE_STACKCHEK was enabled. Reviewed by Amaury Forgeot d'Arc on IRC. --- Python/ceval.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'Python/ceval.c') diff --git a/Python/ceval.c b/Python/ceval.c index 42df3cbb13..dc4276b1bb 100644 --- a/Python/ceval.c +++ b/Python/ceval.c @@ -471,6 +471,7 @@ _Py_CheckRecursiveCall(char *where) return -1; } #endif + _Py_CheckRecursionLimit = recursion_limit; if (tstate->recursion_critical) /* Somebody asked that we don't check for recursion. */ return 0; @@ -489,7 +490,6 @@ _Py_CheckRecursiveCall(char *where) where); return -1; } - _Py_CheckRecursionLimit = recursion_limit; return 0; } -- cgit v1.2.1