Rule down acquisition replay owner strip
This commit is contained in:
parent
7cb9edcf42
commit
8e3800bacb
2 changed files with 16 additions and 0 deletions
|
|
@ -107,6 +107,11 @@ Working rule:
|
|||
`0x004133b0 -> 0x0040e450 / 0x0040ee10` rebuilds cloned local-runtime records and local
|
||||
position/scalar triplets, but current evidence still does not tie that replay family directly
|
||||
to `[site+0x276]`
|
||||
- the same replay strip is narrower than before now:
|
||||
direct local inspection shows `0x0040ee10` only reading cached source lane `[site+0x3cc]`
|
||||
in the checked range, while the bounded `0x00480710` neighborhood is working from
|
||||
`[site+0x04]`, `[site+0x08]`, and `[site+0x3cc]` rather than `[site+0x276]` or the
|
||||
cached tri-lane
|
||||
- the second is narrower in the same way:
|
||||
the checked-in `0x36b1/0x36b2/0x36b3` triplet seam and the
|
||||
`0x4a9d/0x4a3a/0x4a3b` side-buffer seam still do not serialize `[site+0x310/+0x338/+0x360]`
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue