cpython

History

Victor Stinner 63ed5664a1 Issue #14231 : Lib/test/crashers/borrowed_ref_1.py was fixed by ba6376dff6c4.		2012-03-09 13:59:42 +01:00
..
README	Exercise crashers to ensure they are still covering known error cases	2011-03-16 19:52:14 -04:00
bogus_code_obj.py	Merged revisions 77523 via svnmerge from	2010-01-16 15:11:38 +00:00
compiler_recursion.py	Last attempt to get compiler recursion crasher to fail reliably across platforms before giving up and skipping it as unreliably platform dependent	2011-03-19 15:22:59 +10:00
gc_inspection.py	Fix most trivially-findable print statements.	2007-02-09 05:37:30 +00:00
infinite_loop_re.py	Four months of trunk changes (including a few releases...)	2006-12-13 04:49:30 +00:00
mutation_inside_cyclegc.py	Merged revisions 62425-62429,62434-62436,62441,62444,62446-62448,62450-62455,62463,62465-62466,62469,62474,62476-62478,62480,62485,62492,62497-62498,62500,62507,62513-62514,62516,62521,62531,62535,62545-62546,62548-62551,62553-62559,62569,62574,62577,62593,62595,62604-62606,62608,62616,62626-62627,62636,62638,62644-62645,62647-62648,62651-62653,62656,62661,62663,62680,62686-62687,62696,62699-62703,62711 via svnmerge from	2008-05-04 22:42:01 +00:00
recursion_limit_too_high.py	#11515 : fix several typos. Patch by Piotr Kasprzyk.	2011-03-15 05:18:48 +02:00
recursive_call.py	convert shebang lines: python -> python3	2010-03-11 22:53:45 +00:00
underlying_dict.py	another pretty crasher served up by pypy	2011-01-25 00:00:28 +00:00

README

This directory only contains tests for outstanding bugs that cause the
interpreter to segfault.  Ideally this directory should always be empty, but
sometimes it may not be easy to fix the underlying cause and the bug is deemed
too obscure to invest the effort.

Each test should fail when run from the command line:

	./python Lib/test/crashers/weakref_in_del.py

Put as much info into a docstring or comments to help determine the cause of the
failure, as well as a bugs.python.org issue number if it exists.  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.

Also see Lib/test_crashers.py which exercises the crashers in this directory.
In particular, make sure to add any new infinite loop crashers to the black
list so it doesn't try to run them.