Give more info in verbose mode when checking crashers, and stress the stack even...

diff --git a/Lib/test/crashers/compiler_recursion.py b/Lib/test/crashers/compiler_recursion.py
index 8fd93fcdd4960cfa1a149b705a18d87cef0b421b..c00cd6e188ef36ccabb020519f04b75e1573b745 100644 (file)
--- a/Lib/test/crashers/compiler_recursion.py
+++ b/Lib/test/crashers/compiler_recursion.py
@@ -9,5 +9,5 @@ Recorded on the tracker as http://bugs.python.org/issue11383
 # e.g. '1*'*10**5+'1' will die in compiler_visit_expr
 
 # The exact limit to destroy the stack will vary by platform
-# but 100k should do the trick most places
-compile('()'*10**5, '?', 'exec')
+# but 1M should do the trick most places
+compile('()'*10**6, '?', 'exec')

diff --git a/Lib/test/test_crashers.py b/Lib/test/test_crashers.py
index ee612c2bc909debcfde76e6f25c7d1bfceca57dc..86f88f793cf80a8fac39934e9ef9c314fba5ac90 100644 (file)
--- a/Lib/test/test_crashers.py
+++ b/Lib/test/test_crashers.py
@@ -24,6 +24,8 @@ class CrasherTest(unittest.TestCase):
                 continue
             # Some "crashers" only trigger an exception rather than a
             # segfault. Consider that an acceptable outcome.
+            if test.support.verbose:
+                print("Checking crasher:", fname)
             assert_python_failure(fname)