NRSC-5 sanitizer builds¶
The FM and AM ASan manifests are operator-invoked diagnostics for memory-safety defects in RF Sentry's own vendored decoder build. They are not ordinary decoders and never participate in automatic selection or Auto Start.
Pipeline¶
flowchart TB
CAP[Operator-selected live or replay IQ] --> NORMAL[Normal NRSC-5 channelizer]
NORMAL --> ASAN[AddressSanitizer Emscripten module]
ASAN --> OUT[Ordinary protocol output]
ASAN --> FAULT[Source-mapped sanitizer report]
FAULT --> BUNDLE[Bounded diagnostic bundle]
Input rates and bandwidths match the corresponding production FM or AM
manifest. The instrumented module has a heavy cost class and a 1,024 MiB
manifest budget. Its source map is the only intentionally served production
JavaScript/WASM map exception, and only for a content-addressed decoder artifact
under /decoders/.
The adapter, NRSC-5, FFTW and FAAD2/HDC are instrumented together. WASM, hosted
Emscripten loader and privacy-normalized source map have independent catalog
hashes; all are verified before instantiation. The map omits embedded source
and operator home paths while retaining source-oriented fault attribution.
Optimized assertions and sanitizer strings in the WASM binary use neutral
/rfsentry-source / /rfsentry-build roots or relative source paths. The selected
compiler's sysroot and resource headers use /emsdk/sysroot / /emsdk/clang,
including retained DWARF directories when the SDK is installed under a home
directory. The pinned Emscripten compilers do not remap ASan module names, so
translation units use relative input paths, including CMake-built FAAD2/HDC.
Rebuilding changes artifact
hashes; retained fault bundles must still use their exact original artifacts.
Capture, report, and replay¶
Only an explicitly selected sanitizer job retains a 20-second decoder-rate
IQ ring for post-fault download; optimized jobs allocate neither that ring nor
the hosted ASan runtime. The fault report includes build/artifact identity,
input domain/rate/bandwidth, clock quality/epoch/uncertainty, memory and
continuity/drop counters, bounded recent protocol/status context and bounded
runtime output (256 KiB). Report JSON and raw .rfiq replay are separate exports.
Replay must match all three recorded WASM, loader and source-map hashes before consuming samples. Captures/reports stay ignored by Git and carry an operator privacy warning. Do not relabel a mismatched replay as the original fault. Worker-host retrieval is limited to the fixed allowlisted same-origin artifacts; filesystem-like runtime shims are fail-closed, not host capabilities.
Safety and scope¶
Sanitizer replay processes only operator-supplied RF/IQ evidence through the same browser decoder boundary. It does not inspect unrelated processes, credentials, network services, or the appliance filesystem. A sanitizer trap is contained to the decoder worker and produces an inspectable fault rather than crashing the receiver lane.
The distribution and upstream SDK builds of Emscripten 3.1.69 can bundle different compiler/runtime revisions. Qualification applies to the emitted artifacts, not the Emscripten version label alone. Fault bundles identify exact source/build hashes so a report cannot silently refer to a different module.
Ledger and qualification¶
The 6B.5 diagnostic evidence records the pinned FM fixture, browser-artifact instantiation, source-mapped test fault and deterministic replay qualification. The deliberate fault trigger is fixture-only, never part of a published decoder. Live reproduction, fault capture/replay and confirmation of receiver/audio/display isolation remain operator gates. Dated memory/throughput results describe that diagnostic fixture, not normal jobs or the current host.