Expand description
The region runtime for owned Rust probes, and its strict reader.
Each instrumented crate carries a copy of the runtime
(runtime-assets/rust-region-runtime.rs); every copy in a process maps
one region, a slot per probe holding its first sighting’s sequence and
thread. The runtime never computes coverage: the reader rebuilds the
records in execution order and the evidence model takes them from there.
Structs§
- Rust
Probe Entry - One record a process wrote, with the thread that wrote it. Records come back in execution order, but a test that spawns threads interleaves them: an assertion witnesses its own thread’s records and no other’s.
Enums§
Functions§
- parse_
rust_ region - One region, read back as the records its process wrote, in the order it wrote them: each slot holds its first sighting’s sequence and thread, and the overflow file beside it the decision combinations the region had no room for. Pages the bitmap says no probe touched are not read.
- parse_
rust_ region_ cfgs - What the builds of a run said of each
cfggate: bit 0 some crate was built without the gated code, bit 1 some crate with it. Zero: no process of a crate holding it ever mapped a region, and the run cannot tell. - read_
rust_ cfg_ settlement - Every region of
token’s instrumentation underroot, at any depth – a run keeps a directory per test – with what each said of thecfggates, accumulated. - read_
rust_ region_ directory - Every region of
token’s instrumentation in a test’s evidence directory – one per process the test ran – read back as records, by file name. A region another instrumentation wrote (a fixture instrumented on its own inside the workspace) is not this run’s and is left out. - render_
rust_ region_ runtime - The region runtime for one crate root. Every crate of an instrumentation
shares
tokenandlayout, so their copies map one region per process.crate_keynames the crate’s exports where the region is static memory (wasm): each crate of a module keeps its own there.