• Home
Name Date Size #Lines LOC

..--

READMED03-May-2024838 1712

bogus_code_obj.pyD03-May-2024619 2014

borrowed_ref_1.pyD03-May-2024398 3023

borrowed_ref_2.pyD03-May-2024644 3929

buffer_mutate.pyD03-May-2024873 319

compiler_recursion.pyD03-May-202481 64

decref_before_assignment.pyD03-May-20241,020 4534

gc_has_finalizer.pyD03-May-2024724 3726

gc_inspection.pyD03-May-20241.1 KiB3323

infinite_loop_re.pyD03-May-2024645 179

loosing_mro_ref.pyD03-May-20241.1 KiB3622

mutation_inside_cyclegc.pyD03-May-2024753 3214

nasty_eq_vs_dict.pyD03-May-20241 KiB4828

recursion_limit_too_high.pyD03-May-2024779 174

recursive_call.pyD03-May-2024357 165

warnings_del_crasher.pyD03-May-2024873 3023

README

1This directory only contains tests for outstanding bugs that cause the
2interpreter to segfault.  Ideally this directory should always be empty, but
3sometimes it may not be easy to fix the underlying cause and the bug is deemed
4too obscure to invest the effort.
5
6Each test should fail when run from the command line:
7
8	./python Lib/test/crashers/weakref_in_del.py
9
10Put as much info into a docstring or comments to help determine the cause of the
11failure, as well as a bugs.python.org issue number if it exists.  Particularly
12note if the cause is system or environment dependent and what the variables are.
13
14Once the crash is fixed, the test case should be moved into an appropriate test
15(even if it was originally from the test suite).  This ensures the regression
16doesn't happen again.  And if it does, it should be easier to track down.
17