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

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

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')

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)