Trace Carl lifecycle and add read-only original state observer
This commit is contained in:
1 parent
c642b69849
commit
4cd62d3627
28 files changed
+2387
-5
No files matched your search
@@ -67,12 +67,18 @@ artifacts/jimmy-cutscene-return/rea-completion/. New successful pseudocode:
|
||||
|438A60 retained-mode input dispatch|ev_77ee22e6d49adc0c983af92ba74273faf5f4daf697ab520ea45d22b08bc11bcb|
|
||||
|42AE00 cleanup wrapper|ev_2ee50b10018363378445be32df38ab4f6b2125247b69485304867674d5d484da|
|
||||
|
||||
DEFAULT entry447CF0 did not resolve to a Ghidra procedure; the provider then
|
||||
DEFAULT entry447CF0 did not resolve to a Ghidra procedure in the original PE database; the provider then
|
||||
reported the numeric selector as an unmapped file offset. Its complete error is
|
||||
retained as00.json; no pseudocode is attributed to it. The guarded retained REA
|
||||
instructions support the DEFAULT statements above. No unchanged retry or claim
|
||||
that the whole original was executed follows from that provider result.
|
||||
|
||||
2026-11-06: a changed input strategy now supplies complete DEFAULT pseudocode
|
||||
through a separately mapped static raw carrier. Its Evidence subject and mapping
|
||||
are explicit in [the DEFAULT recovery report](jimmy-default-decompilation.md).
|
||||
The original PE function-boundary failure remains recorded; the carrier result
|
||||
agrees with the guarded instructions and supplies no additional Jimmy reset.
|
||||
|
||||
## Port cause versus original explanation
|
||||
|
||||
[The port diagnostic](jimmy-cutscene-port-trace.md) reproduces48 cases. On fresh
|
||||
|
||||
Reference in new issue
Block a user