Files
RedBear-OS/local/recipes/dev/libclc/source/llvm/test/DebugInfo/dwarfdump-ranges.test
T
vasilito cb424d7448 build: static patch-sanity linter (shift-left the malformed-patch class)
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).
2026-08-01 05:13:02 +03:00

25 lines
877 B
Plaintext

RUN: llvm-dwarfdump -v %p/Inputs/dwarfdump-test4.elf-x86-64 | FileCheck %s
CHECK: .debug_info contents:
CHECK: DW_TAG_compile_unit
CHECK-NOT: TAG
CHECK: DW_AT_ranges [DW_FORM_data4] (0x00000000
CHECK-NEXT: [0x000000000000062c, 0x0000000000000637)
CHECK-NEXT: [0x0000000000000637, 0x000000000000063d))
CHECK: DW_TAG_compile_unit
CHECK-NOT: TAG
CHECK: DW_AT_ranges [DW_FORM_data4] (0x00000030
CHECK-NEXT: [0x0000000000000640, 0x000000000000064b)
CHECK-NEXT: [0x0000000000000637, 0x000000000000063d))
CHECK: .debug_ranges contents:
CHECK-NEXT: 00000000 000000000000062c 0000000000000637
CHECK-NEXT: 00000000 0000000000000637 000000000000063d
CHECK-NEXT: 00000000 <End of list>
CHECK-NEXT: 00000030 0000000000000640 000000000000064b
CHECK-NEXT: 00000030 0000000000000637 000000000000063d
CHECK-NEXT: 00000030 <End of list>