Liste des Groupes | Revenir à theory |
Am Fri, 18 Oct 2024 12:11:17 -0500 schrieb olcott:On 10/18/2024 12:00 PM, joes wrote:Am Fri, 18 Oct 2024 11:39:52 -0500 schrieb olcott:Until if (root) is true it has no effect on DDD emulated by HHH.On 10/18/2024 9:41 AM, joes wrote:What? That is part of HHH, not DDD.Am Fri, 18 Oct 2024 09:10:04 -0500 schrieb olcott:That has nothing to do with any aspect of the emulation until HHH hasOn 10/18/2024 6:17 AM, Richard Damon wrote:>On 10/17/24 11:47 PM, olcott wrote:On 10/17/2024 10:27 PM, Richard Damon wrote:On 10/17/24 9:47 PM, olcott wrote:On 10/17/2024 8:13 PM, Richard Damon wrote:On 10/17/24 7:31 PM, olcott wrote:>When DDD is correctly emulated by HHH according to the
semantics of the x86 language DDD cannot possibly reach its
own machine address [00002183] no matter what HHH does.
+-->[00002172]-->[00002173]-->[00002175]-->[0000217a]--+>Except that 0000217a doesn't go to 00002172, but to 000015d2The more interesting part is HHH simulating itself, specifically theThe Emulating HHH sees those addresses at its begining and thenOK great this is finally good progress.
never again.
Then the HHH that it is emulating will see those addresses, but not
the outer one that is doing that emulation of HHH.
And so on.
Which HHH do you think EVER gets back to 00002172?
What instruction do you think that it emulates that would tell it
to do so?
At best the trace is:
00002172 00002173 00002175 0000217a conditional emulation of
00002172 conditional emulation of 00002173 conditional emulation of
00002175 conditional emulation of 0000217a CE of CE of 00002172 ...
if(Root) check on line 502.
correctly emulated itself emulating DDD.
The existence of the check has an effect right from the start;So maybe you have ADD too. You can't seem to pay
besides, it is true the first time it is executed.
Les messages affichés proviennent d'usenet.