cpython/Lib/test/crashers
Georg Brandl 7cae87ca7b Patch #1550800: make exec a function. 2006-09-06 06:51:57 +00:00
..
README Merge p3yk branch with the trunk up to revision 45595. This breaks a fair 2006-04-21 10:40:58 +00:00
bogus_code_obj.py Patch #1550800: make exec a function. 2006-09-06 06:51:57 +00:00
borrowed_ref_1.py Merged revisions 46753-51188 via svnmerge from 2006-08-11 14:57:12 +00:00
borrowed_ref_2.py Merged revisions 46753-51188 via svnmerge from 2006-08-11 14:57:12 +00:00
dangerous_subclassing.py collected my segfaulting Python examples from the SF trackers 2006-01-14 10:58:30 +00:00
gc_inspection.py Merged revisions 46753-51188 via svnmerge from 2006-08-11 14:57:12 +00:00
infinite_rec_1.py collected my segfaulting Python examples from the SF trackers 2006-01-14 10:58:30 +00:00
infinite_rec_2.py collected my segfaulting Python examples from the SF trackers 2006-01-14 10:58:30 +00:00
infinite_rec_5.py collected my segfaulting Python examples from the SF trackers 2006-01-14 10:58:30 +00:00
loosing_dict_ref.py collected my segfaulting Python examples from the SF trackers 2006-01-14 10:58:30 +00:00
modify_dict_attr.py collected my segfaulting Python examples from the SF trackers 2006-01-14 10:58:30 +00:00
nasty_eq_vs_dict.py Merge p3yk branch with the trunk up to revision 45595. This breaks a fair 2006-04-21 10:40:58 +00:00
recursion_limit_too_high.py Merged revisions 46753-51188 via svnmerge from 2006-08-11 14:57:12 +00:00
recursive_call.py Merged revisions 46753-51188 via svnmerge from 2006-08-11 14:57:12 +00:00
weakref_in_del.py Set svn:eol-style to native. 2006-03-01 06:19:04 +00:00

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.