Bind acquisition owner writes to opcode dispatcher
This commit is contained in:
parent
78ccee53a3
commit
49ee76ef2a
2 changed files with 45 additions and 3 deletions
|
|
@ -142,6 +142,15 @@ Working rule:
|
|||
`0x004269b0 / 0x00426a10`, the create-side `0x0040ef10 / 0x0040f6d0` strip, and the bulk
|
||||
reassignment families `0x00426dce..0x00426ea1` and `0x00430040..0x004300d6`, not under the
|
||||
known `0x00444690 -> 0x004133b0 -> 0x0040ee10` replay strip
|
||||
- the same write side is now grounded one level higher too:
|
||||
direct local control-flow reconstruction shows those families hanging under the grouped opcode
|
||||
dispatcher `0x00431b20` over `0x0061039c`, with opcodes `0x04..0x07` dispatching to
|
||||
`0x00430040`, opcodes `0x08/0x10..0x13` dispatching to `0x00426d60`, and opcodes
|
||||
`0x0d/0x16` dispatching to `0x0042fc90`
|
||||
- `0x0042fc90` itself is now ruled onto the live mutation side too:
|
||||
it iterates the live placed-structure collection `0x0062b26c`, filters rows through
|
||||
`0x0040c990`, optional owner-company match `[site+0x276]`, and row vtable slot `+0x70`,
|
||||
which keeps that branch on the live application side rather than replay
|
||||
- the create-side family is grounded separately too:
|
||||
city-connection direct placement already reaches
|
||||
`0x00402cb0 -> 0x00403ed5/0x0040446b -> 0x004134d0 -> 0x0040ef10`
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue