vasilito
cb424d7448
verify-patch-sanity.py validates every active recipe .patch has internally- consistent hunk line counts — catching the 'malformed patch at line N' failure at commit/CI/preflight time instead of hours into a cook. This cycle hit that class three times (qtwaylandscanner, sddm, xwayland), each only discovered when cookbook tried to apply the patch. Running it across the repo found 29 latent malformed patches (validated against GNU patch: e.g. relibc/P3-sysv-ipc reproduces 'malformed patch at line 22'). They were harmless only because they sit in vendored recipes (baked, not re- applied) — but would fail on any version-bump re-derivation. --fix recounts the hunk headers (body untouched) and repaired all 29. Wired into build-preflight.sh (Phase 1.0D) and redbear-ci.yml, with a unit test (test-patch-sanity.sh). Skips archived/legacy trees and unvalidatable formats (empty placeholders, bare-@@ git hunks).
19 lines
871 B
ReStructuredText
19 lines
871 B
ReStructuredText
Fuzzing for LLVM-libc functions
|
|
===============================
|
|
|
|
Fuzz tests are used to ensure quality and security of LLVM-libc implementations.
|
|
All fuzz tests live under the directory named ``fuzzing``. Within this
|
|
directory, the fuzz test for a libc function lives in the same nested directory
|
|
as its implementation in the toplevel ``src`` directory. The build target
|
|
``libc-fuzzer`` builds all of the enabled fuzz tests (but does not run them).
|
|
|
|
Types of fuzz tests
|
|
===================
|
|
|
|
As of this writing, there are two different kinds of fuzz tests. One kind are
|
|
the traditional fuzz tests which test one function at a time and only that
|
|
particular function. The other kind of tests are what we call as the
|
|
differential fuzz tests. These tests compare the behavior of LLVM libc
|
|
implementations with the behavior of the corresponding functions from the system
|
|
libc.
|