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

This commit is contained in:
Nick Coghlan 2011-03-17 11:04:34 -04:00
parent 589e8d9b12
commit f694a409aa
2 changed files with 4 additions and 2 deletions

View file

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

View file

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