Liste des Groupes | Revenir à theory |
Am Sat, 07 Jun 2025 11:02:55 -0500 schrieb olcott:That is not the question being answered.On 6/7/2025 10:54 AM, wij wrote:On Sat, 2025-06-07 at 10:35 -0500, olcott wrote:On 6/7/2025 10:31 AM, wij wrote:On Sat, 2025-06-07 at 09:57 -0500, olcott wrote:On 6/7/2025 9:54 AM, wij wrote:On Sat, 2025-06-07 at 09:32 -0500, olcott wrote:What do you mean by "then" and "once"? That implies completion andThe execution trace of HHH1(DDD) shows the divergence of DDD
emulated by HHH from DDD emulated by HHH1.
Shows that DDD emulated by HHH and DDD emulated by HHH1 diverges
as soon as HHH begins emulating itself emulating DDD.
>
*From the execution trace of HHH1(DDD) shown below*
DDD emulated by HHH1 DDD emulated by HHH [00002183]
push ebp [00002183] push ebp [00002184] mov
ebp,esp [00002184] mov ebp,esp [00002186] push 00002183
; DDD [00002186] push 00002183 ; DDD [0000218b] call 000015c3 ;
HHH [0000218b] call 000015c3 ; HHH *HHH1 emulates DDD once then
HHH emulates DDD once, these match*
succession, however we are only ever simulating a single call, and
only HHH1 simulates any returns of DDD/HHH.
HHH1 simulates DDD completely, HHH recurses and aborts *inside*. HHH
does not simulate DDD once, it only enters the call, but never exits.
At those addresses we have the first instruction of DDD and the one afterThe next instruction of DDD that HHH emulates is at the machine
address of 00002183.
The next instruction of DDD that HHH1 emulates is at the machine
address of 00002190.
the call, respectively.
[main -> HHH1(DDD) -> HHH(DDD) -> HHH(DDD)]HHH1 does simulate HHH simulating DDD.New slave_stack at:198d21 DDD emulated by HHH *This is the
beginning of the divergence of the behavior*
*HHH is emulating itself emulating DDD, HHH1 never does that*
Les messages affichés proviennent d'usenet.