Liste des Groupes | Revenir à theory |
Am Thu, 04 Jul 2024 11:29:10 -0500 schrieb olcott:On 7/4/2024 11:24 AM, joes wrote:Am Thu, 04 Jul 2024 10:58:03 -0500 schrieb olcott:The x86utm operating system spawns a separate process so thatOn 7/4/2024 10:03 AM, joes wrote:Am Thu, 04 Jul 2024 08:32:10 -0500 schrieb olcott:On 7/4/2024 8:09 AM, joes wrote:Huh? HHH examines main. Sure, it doesn’t /simulate/ the return.Am Thu, 04 Jul 2024 07:53:07 -0500 schrieb olcott:That is not the one that HHH examines.On 7/4/2024 6:09 AM, joes wrote:I was talking about main itself.Am Wed, 03 Jul 2024 10:55:14 -0500 schrieb olcott:main correctly simulated by H never returns.On 7/3/2024 10:52 AM, Fred. Zwarts wrote:As a matter of fact, H does abort it. H then returns to main,Similarly, if you think that HHH can simulate itself correctly,main correctly emulated by H never stops running unless aborted.
you are wrong.
int H(ptr p, ptr i);
int main()
{
return H(main, 0);
}
You showed that H returns, but that the simulation thinks it
does not return.
which then stops running.
H can emulate another different instance of D in this separate process.
H must call DebugTrace()
to switch process contexts to emulate one more instruction of D.
Oh, there should also be different instances of H.There are. DDD and the HHH that DDD calls are in the
It makes no sense only if you are totally clueless of operating systemThere is more than one main() process. One of them cannot possiblyThat makes no sense. They have exactly the same code.
halt and the other one halts.
process contexts.
What is their difference?When the directly executed DDD calls HHH(DDD) the
Les messages affichés proviennent d'usenet.