bb0f990de9
gen_addresses.py distinguishes "addr" (VA -> RVA) from "offset" (a member offset). Three lane-K entries used "addr" for offsets and generated negative RVAs, which broke the engine build. Two are re-expressed as offsets; the third, StrategyServer_off_RNGPtr_S_frame, is withdrawn - addresses.json already has StrategyServer_off_RNG = 0x16c for the S frame alongside off_RNGPtr = 0x168 for S+4, which is precisely lane T's rule. The second call site found this lane confirms it rather than correcting it. |
||
|---|---|---|
| .. | ||
| lane-a.json | ||
| lane-k.json | ||
| lane-o.json | ||
| lane-t.json | ||
| lane-u.json | ||
| lane-w.json | ||
| README.md | ||
Per-lane address fragments
addresses.json is a single shared file. When several lanes run concurrently they edit the
same lines, and three times on 2026-09-08 one lane's git add swept another's in-flight
entries into the wrong commit. Nothing was lost, but authorship and atomicity were.
A lane may instead drop its own file here:
{ "entries": [ { "name": "...", "addr": "0x...", "convention": "...",
"prototype": "...", "status": "verified", "source": "findings/..." } ] }
Name it after the lane (lane-d.json). tools/gen_addresses.py merges every fragment in
sorted order after addresses.json. A duplicate name across files is a hard error, not
last-wins — two lanes disagreeing about an address is exactly the thing we must not paper over.
The integrator folds fragments back into addresses.json once the lane's work is merged.