cpython

History

Serhiy Storchaka e0ed2d75c8 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.		2014-01-16 18:59:17 +02:00
..
README	Merged revisions 87050,87101,87146,87156,87172,87175,87371,87378,87522-87524,87526,87530-87535 via svnmerge from	2011-02-25 10:50:32 +00:00
bogus_code_obj.py	…
borrowed_ref_1.py	…
borrowed_ref_2.py	…
buffer_mutate.py	Added a new crasher that targets mutating the underlying storage of a buffer. All work done by Armin Rigo.	2012-03-30 08:45:25 -04:00
compiler_recursion.py	Ivan on IRC in #twisted reported this crasher.	2009-02-06 11:46:26 +00:00
decref_before_assignment.py	Add a crasher for the documented issue of calling "Py_DECREF(self->xxx)";	2012-03-04 18:56:23 +01:00
gc_has_finalizer.py	An example that shows that _PyInstance_Lookup() does not fulfill	2010-09-03 09:26:14 +00:00
gc_inspection.py	…
infinite_loop_re.py	…
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
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	#11515 : fix several typos. Patch by Piotr Kasprzyk.	2011-03-15 18:55:01 +02:00
recursive_call.py	Issue #19936 : Added executable bits or shebang lines to Python scripts which	2014-01-16 18:59:17 +02: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.