mirror of https://github.com/python/cpython
f343e01c17
svn+ssh://pythondev@svn.python.org/python/trunk ........ r68560 | amaury.forgeotdarc | 2009-01-13 00:36:55 +0100 (mar., 13 janv. 2009) | 6 lines #3720: Interpreter crashes when an evil iterator removes its own next function. Now the slot is filled with a function that always raises. Will not backport: extensions compiled with 2.6.x would not run on 2.6.0. ........ |
||
---|---|---|
.. | ||
README | ||
bogus_code_obj.py | ||
bogus_sre_bytecode.py | ||
borrowed_ref_1.py | ||
borrowed_ref_2.py | ||
gc_inspection.py | ||
infinite_loop_re.py | ||
loosing_mro_ref.py | ||
multithreaded_close.py | ||
mutation_inside_cyclegc.py | ||
nasty_eq_vs_dict.py | ||
recursion_limit_too_high.py | ||
recursive_call.py |
README
This directory only contains tests for outstanding bugs that cause the interpreter to segfault. Ideally this directory should always be empty. Sometimes it may not be easy to fix the underlying cause. Each test should fail when run from the command line: ./python Lib/test/crashers/weakref_in_del.py Each test should have a link to the bug report: # http://python.org/sf/BUG# Put as much info into a docstring or comments to help determine the cause of the failure. Particularly note if the cause is system or environment dependent and what the variables are. Once the crash is fixed, the test case should be moved into an appropriate test (even if it was originally from the test suite). This ensures the regression doesn't happen again. And if it does, it should be easier to track down.