cpython

History

Brett Cannon 22565aac3b An object with __call__ as an attribute, when called, will have that attribute checked for __call__ itself, and will continue to look until it finds an object without the attribute. This can lead to an infinite recursion. Closes bug #532646, again. Will be backported.		2006-06-09 22:31:23 +00:00
..
README	Copy note from leakers README here too. We want to keep all test cases.	2006-04-14 06:35:46 +00:00
coerce.py	…
dangerous_subclassing.py	collected my segfaulting Python examples from the SF trackers	2006-01-14 10:58:30 +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_4.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	add a very old crasher from the 2.1 -> 2.2 round of dictionary fixes.	2006-04-18 13:52:32 +00:00
recursive_call.py	add another crash reported by Thomas Wouters	2006-01-11 07:21:19 +00:00
weakref_in_del.py	Set svn:eol-style to native.	2006-03-01 06:19:04 +00:00
xml_parsers.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.