cpython

History

Armin Rigo dcde494114 A collection of crashers, all variants of the idea of issue #3720.		2008-08-29 21:21:52 +00:00
..
README	…
bogus_code_obj.py	Document the crashers that will not go away soon as "won't fix",	2006-07-25 18:38:39 +00:00
bogus_sre_bytecode.py	The regular expression engine in '_sre' can segfault when interpreting	2006-08-25 12:44:28 +00:00
borrowed_ref_1.py	…
borrowed_ref_2.py	…
gc_inspection.py	…
infinite_loop_re.py	Add a "crasher" taken from the sgml bug report referenced in the comment	2006-09-11 04:32:57 +00:00
iter.py	A collection of crashers, all variants of the idea	2008-08-29 21:21:52 +00:00
loosing_mro_ref.py	Sounds obvious, but I didn't even realize that you can put non-string	2008-06-12 09:50:58 +00:00
multithreaded_close.py	Add a crasher for the long-standing issue with closing a file	2007-10-21 09:14:15 +00:00
mutation_inside_cyclegc.py	A new crasher.	2008-04-25 09:35:18 +00:00
nasty_eq_vs_dict.py	…
recursion_limit_too_high.py	…
recursive_call.py	Document the crashers that will not go away soon as "won't fix",	2006-07-25 18:38:39 +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.