09677946cb
Use one machine-supported oracle for traditional, direct atomic and server Code Mode workflows. Include pointer/stack passing, local strict-checking routing and return-width limits without requiring native-only identities. Co-authored-by: gensokyo-dev <342580529+gensokyo-dev@users.noreply.github.com> Co-authored-by: Kaoru0822 <208281322+kaoru0822-kitauji@users.noreply.github.com>
29 lines
1.7 KiB
Plaintext
29 lines
1.7 KiB
Plaintext
Analyze {{artifact_path}} statically, starting from these observed formats:
|
|
- REMOTE HOST IDENTIFICATION HAS CHANGED
|
|
- Host key for %.200s has changed and you have requested strict checking.
|
|
|
|
Find the function that supplies the banner format to a formatting/logging call,
|
|
and the caller that owns the second diagnostic. Establish both from references;
|
|
do not identify functions by a guessed original source name. Show the selected
|
|
direct call from that caller into the warning function. Trace its passed pointer
|
|
into the warning function's first helper-call use, with the machine passing
|
|
location and call targets. If using SSA, keep each function's value identities
|
|
separate and distinguish matching storage from a general alias proof.
|
|
|
|
Show how the banner format pointer is passed to its formatting/logging call.
|
|
Verify the essential setup, stack location and transfer against focused machine
|
|
instructions. Recovered origins/slots alone do not establish machine addresses
|
|
or original source parameter ordinals.
|
|
|
|
In the selected caller, after the warning call returns, identify the local test
|
|
that chooses the strict-checking diagnostic versus continuation. Report the
|
|
tested storage address and width, zero/nonzero behavior, both actual machine
|
|
successors, and the selected failure-cleanup path's low 32-bit return value.
|
|
Does selecting the banner alone prove rejection? Does the zero branch prove
|
|
that a connection will be accepted?
|
|
|
|
Give a focused answer with function/instruction addresses, real Evidence IDs,
|
|
target digest and necessary coverage. Prefer selected facts/windows; do not
|
|
return full reports or inventories to model context. Preserve unknown runtime
|
|
values, memory aliases, logging behavior, other paths and runtime feasibility.
|