Changeset 391 for python/trunk/Lib/test/crashers
- Timestamp:
- Mar 19, 2014, 11:31:01 PM (11 years ago)
- Location:
- python/trunk
- Files:
-
- 3 deleted
- 3 edited
- 4 copied
Legend:
- Unmodified
- Added
- Removed
-
python/trunk
-
Property svn:mergeinfo
set to
/python/vendor/Python-2.7.6 merged eligible /python/vendor/current merged eligible
-
Property svn:mergeinfo
set to
-
python/trunk/Lib/test/crashers/README
r2 r391 1 This directory only contains tests for outstanding bugs that cause 2 the interpreter to segfault. Ideally this directory should always 3 be empty. Sometimes it may not be easy to fix the underlying cause. 1 This directory only contains tests for outstanding bugs that cause the 2 interpreter to segfault. Ideally this directory should always be empty, but 3 sometimes it may not be easy to fix the underlying cause and the bug is deemed 4 too obscure to invest the effort. 4 5 5 6 Each test should fail when run from the command line: … … 7 8 ./python Lib/test/crashers/weakref_in_del.py 8 9 9 Each test should have a link to the bug report: 10 Put as much info into a docstring or comments to help determine the cause of the 11 failure, as well as a bugs.python.org issue number if it exists. Particularly 12 note if the cause is system or environment dependent and what the variables are. 10 13 11 # http://python.org/sf/BUG# 12 13 Put as much info into a docstring or comments to help determine 14 the cause of the failure. Particularly note if the cause is 15 system or environment dependent and what the variables are. 16 17 Once the crash is fixed, the test case should be moved into an appropriate 18 test (even if it was originally from the test suite). This ensures the 19 regression doesn't happen again. And if it does, it should be easier 20 to track down. 14 Once the crash is fixed, the test case should be moved into an appropriate test 15 (even if it was originally from the test suite). This ensures the regression 16 doesn't happen again. And if it does, it should be easier to track down. -
python/trunk/Lib/test/crashers/recursion_limit_too_high.py
r2 r391 6 6 7 7 # The point of this example is to show that sys.setrecursionlimit() is a 8 # hack, and not a robust solution. This example simply exerci ces a path8 # hack, and not a robust solution. This example simply exercises a path 9 9 # where it takes many C-level recursions, consuming a lot of stack 10 10 # space, for each Python-level recursion. So 1000 times this amount of
Note:
See TracChangeset
for help on using the changeset viewer.