cpython/Lib/test/crashers
Ezio Melotti 5683a3d85d Merged revisions 77523 via svnmerge from
svn+ssh://pythondev@svn.python.org/python/branches/py3k

........
  r77523 | ezio.melotti | 2010-01-16 17:09:48 +0200 (Sat, 16 Jan 2010) | 1 line

  Fixed crasher. Patch by Florent Xicluna.
........
2010-01-16 15:11:38 +00:00
..
README
bogus_code_obj.py Merged revisions 77523 via svnmerge from 2010-01-16 15:11:38 +00:00
borrowed_ref_1.py
borrowed_ref_2.py Removed the API to create unbound methods and simplified the API for bound methods. The signature is PyMethod_New(func, instance). 2007-11-27 10:40:20 +00:00
compiler_recursion.py Merged revisions 69364-69365,69409-69410,69413,69417,69435,69442,69447,69495,69519-69521 via svnmerge from 2009-02-13 02:50:59 +00:00
gc_inspection.py
infinite_loop_re.py
loosing_mro_ref.py Issue #1717: Remove cmp. Stage 1: remove all uses of cmp and __cmp__ from 2009-01-27 18:17:45 +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
nasty_eq_vs_dict.py
recursion_limit_too_high.py
recursive_call.py

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.