cpython

History

Serhiy Storchaka b992a0e102 Issue #19936 : Added executable bits or shebang lines to Python scripts which requires them. Disable executable bits and shebang lines in test and benchmark files in order to prevent using a random system python, and in source files of modules which don't provide command line interface. Fixed shebang line to use python3 executable in the unittestgui script.		2014-01-16 17:15:49 +02: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
gc_inspection.py	…
infinite_loop_re.py	…
mutation_inside_cyclegc.py	…
recursive_call.py	Issue #19936 : Added executable bits or shebang lines to Python scripts which	2014-01-16 17:15:49 +02:00
trace_at_recursion_limit.py	Record a known crasher from #6717	2012-11-05 21:26:57 +10: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.