traverseda
/
cpython
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
cpython/Lib/test/crashers
History
Brett Cannon ea3912b0da If a classic class defined a __coerce__() method that just returned its two 
arguments in reverse, the interpreter would infinitely recourse trying to get a
coercion that worked.  So put in a recursion check after a coercion is made and
the next call to attempt to use the coerced values.

Fixes bug #992017 and closes crashers/coerce.py .
 		2006-06-13 21:46:41 +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
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
…
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.