RedBear-OS

Files

T

vasilito ff4ff35918 feat: track all source trees in git — full fork offline-first model

Red Bear OS is a full fork. All sources must be available from git clone
with zero network access. Removed gitignore rules that excluded fetched
source trees under recipes/*/source/, local/recipes/kde/*/source/,
local/recipes/qt/*/source/, and vendor source trees.

Build artifacts (target/, build/, source.tar, *.o, *.so) remain excluded.

127291 files added — kernel, relibc, base, bootloader, pkgar, all KDE/Qt
frameworks, mesa, wayland, DRM drivers, and every other recipe source.

2026-05-14 10:55:53 +01:00

bogus_code_obj.py

feat: track all source trees in git — full fork offline-first model

2026-05-14 10:55:53 +01:00

gc_inspection.py

feat: track all source trees in git — full fork offline-first model

2026-05-14 10:55:53 +01:00

infinite_loop_re.py

feat: track all source trees in git — full fork offline-first model

2026-05-14 10:55:53 +01:00

mutation_inside_cyclegc.py

feat: track all source trees in git — full fork offline-first model

2026-05-14 10:55:53 +01:00

README

feat: track all source trees in git — full fork offline-first model

2026-05-14 10:55:53 +01:00

recursive_call.py

feat: track all source trees in git — full fork offline-first model

2026-05-14 10:55:53 +01:00

trace_at_recursion_limit.py

feat: track all source trees in git — full fork offline-first model

2026-05-14 10:55:53 +01:00

underlying_dict.py

feat: track all source trees in git — full fork offline-first model

2026-05-14 10:55:53 +01: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 an issue number or link 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.