Rocksolid Light

Welcome to novaBBS (click a section below)

mail  files  register  newsreader  groups  login

Message-ID:  

It is easier to write an incorrect program than understand a correct one.


computers / comp.ai.philosophy / Re: Technically competent Software engineers can verify this halting problem proof refutation [ full closure ]

Re: Technically competent Software engineers can verify this halting problem proof refutation [ full closure ]

<0J6dnT5xBam-gCj_nZ2dnUU7_81g4p2d@giganews.com>

  copy mid

https://www.novabbs.com/computers/article-flat.php?id=9735&group=comp.ai.philosophy#9735

  copy link   Newsgroups: comp.theory comp.ai.philosophy sci.logic sci.math
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.misty.com!border2.nntp.dca1.giganews.com!nntp.giganews.com!buffer2.nntp.dca1.giganews.com!news.giganews.com.POSTED!not-for-mail
NNTP-Posting-Date: Thu, 23 Jun 2022 21:10:43 -0500
Date: Thu, 23 Jun 2022 21:10:41 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
Thunderbird/91.10.0
Subject: Re: Technically competent Software engineers can verify this halting
problem proof refutation [ full closure ]
Content-Language: en-US
Newsgroups: comp.theory,comp.ai.philosophy,sci.logic,sci.math
References: <EOydnaeszcdfHS__nZ2dnUU7_83NnZ2d@giganews.com>
<20220622203106.00003fa2@reddwarf.jmc>
<xqSdnb2KKdOL5i7_nZ2dnUU7_81g4p2d@giganews.com>
<TwOsK.191531$JVi.174704@fx17.iad>
<N5WdnY_iDptAKC7_nZ2dnUU7_8xh4p2d@giganews.com>
<nLOsK.9452$mY1.1924@fx01.iad>
<3LmdnVllU6W8Jy7_nZ2dnUU7_8xh4p2d@giganews.com>
<j8PsK.15112$%i2.4898@fx48.iad>
<s9CdndzLkud5XC7_nZ2dnUU7_83NnZ2d@giganews.com>
<%sPsK.15923$nZ1.10923@fx05.iad>
<NZmdnRE_I-AmWS7_nZ2dnUU7_81g4p2d@giganews.com>
<RAPsK.191532$JVi.129665@fx17.iad>
<jeKdndsSjJTDUC7_nZ2dnUU7_83NnZ2d@giganews.com>
<SiQsK.193267$70j.57451@fx16.iad>
<x9KdnSlyYIyxSy7_nZ2dnUU7_8zNnZ2d@giganews.com>
<3iRsK.3746$vd2.1411@fx39.iad>
<7t6dnRsAGcTtay7_nZ2dnUU7_83NnZ2d@giganews.com>
<f7da38b3-168a-4447-b3bf-5ebb1d57251dn@googlegroups.com>
<TdWdnWBGBqYViCj_nZ2dnUU7_83NnZ2d@giganews.com>
<2U8tK.9437$Me2.4193@fx47.iad>
From: NoO...@NoWhere.com (olcott)
In-Reply-To: <2U8tK.9437$Me2.4193@fx47.iad>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Message-ID: <0J6dnT5xBam-gCj_nZ2dnUU7_81g4p2d@giganews.com>
Lines: 244
X-Usenet-Provider: http://www.giganews.com
X-Trace: sv3-vkOXJJfHdIMQbrs1cXyXTIaBw9d3vvNwV6gWXdWa9Nubcc/0WqqQunBCTL394JQF12/K/sIVVPGLSQC!Uin1b8XgaBwQVXfaMCc1I+bS+qFyKn3ckB97oyta3dij0V+NNfddU6092pu0bv0S03cIBW9hU5vh
X-Complaints-To: abuse@giganews.com
X-DMCA-Notifications: http://www.giganews.com/info/dmca.html
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
X-Original-Bytes: 13154
 by: olcott - Fri, 24 Jun 2022 02:10 UTC

On 6/23/2022 8:59 PM, Richard Damon wrote:
>
> On 6/23/22 9:38 PM, olcott wrote:
>> On 6/23/2022 6:55 PM, dklei...@gmail.com wrote:
>>> On Wednesday, June 22, 2022 at 10:13:27 PM UTC-7, olcott wrote:
>>>> On 6/22/2022 10:41 PM, Richard Damon wrote:
>>>>> On 6/22/22 10:55 PM, olcott wrote:
>>>>>> On 6/22/2022 9:34 PM, Richard Damon wrote:
>>>>>>> On 6/22/22 10:18 PM, olcott wrote:
>>>>>>>> On 6/22/2022 8:45 PM, Richard Damon wrote:
>>>>>>>>> On 6/22/22 9:41 PM, olcott wrote:
>>>>>>>>>> On 6/22/2022 8:36 PM, Richard Damon wrote:
>>>>>>>>>>> On 6/22/22 9:29 PM, olcott wrote:
>>>>>>>>>>>> On 6/22/2022 8:14 PM, Richard Damon wrote:
>>>>>>>>>>>>> On 6/22/22 8:55 PM, olcott wrote:
>>>>>>>>>>>>>> On 6/22/2022 7:48 PM, Richard Damon wrote:
>>>>>>>>>>>>>>> On 6/22/22 8:37 PM, olcott wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> First you agree that my words are perfectly correct within
>>>>>>>>>>>>>>>> their specified context
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Since you haven't actualy defined you context, and imply
>>>>>>>>>>>>>>> that
>>>>>>>>>>>>>>> it is the halting problem, where they can not be correct,
>>>>>>>>>>>>>>> that is not possible.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> First you agree that these words are 100% correct within the
>>>>>>>>>>>>>> context of software engineering totally ignoring the context
>>>>>>>>>>>>>> of the halting problem.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> #include <stdint.h>
>>>>>>>>>>>>>> #define u32 uint32_t
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> #include <stdint.h>
>>>>>>>>>>>>>> typedef void (*ptr)();
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> void P(ptr x)
>>>>>>>>>>>>>> {
>>>>>>>>>>>>>>     if (H(x, x))
>>>>>>>>>>>>>>       HERE: goto HERE;
>>>>>>>>>>>>>>     return;
>>>>>>>>>>>>>> }
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> int main()
>>>>>>>>>>>>>> {
>>>>>>>>>>>>>>     Output("Input_Halts = ", H(P, P));
>>>>>>>>>>>>>> }
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> _P()
>>>>>>>>>>>>>> [000010d2](01)  55              push ebp
>>>>>>>>>>>>>> [000010d3](02)  8bec            mov ebp,esp
>>>>>>>>>>>>>> [000010d5](03)  8b4508          mov eax,[ebp+08]
>>>>>>>>>>>>>> [000010d8](01)  50              push eax
>>>>>>>>>>>>>> [000010d9](03)  8b4d08          mov ecx,[ebp+08]
>>>>>>>>>>>>>> [000010dc](01)  51              push ecx
>>>>>>>>>>>>>> [000010dd](05)  e820feffff      call 00000f02
>>>>>>>>>>>>>> [000010e2](03)  83c408          add esp,+08
>>>>>>>>>>>>>> [000010e5](02)  85c0            test eax,eax
>>>>>>>>>>>>>> [000010e7](02)  7402            jz 000010eb
>>>>>>>>>>>>>> [000010e9](02)  ebfe            jmp 000010e9
>>>>>>>>>>>>>> [000010eb](01)  5d              pop ebp
>>>>>>>>>>>>>> [000010ec](01)  c3              ret
>>>>>>>>>>>>>> Size in bytes:(0027) [000010ec]
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Every sufficiently competent software engineer can easily
>>>>>>>>>>>>>> verify that the complete and correct x86 emulation of the
>>>>>>>>>>>>>> input to H(P,P) by H would never reach the "ret" instruction
>>>>>>>>>>>>>> of P because both H and P would remain stuck in infinitely
>>>>>>>>>>>>>> recursive emulation.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> So, if H actually is a program that does a COMPLETE and
>>>>>>>>>>>>> correct
>>>>>>>>>>>>> x86 emulation of its input, then YES, as I have said many time
>>>>>>>>>>>>> before, this combination is non-halting.
>>>>>>>>>>>>>
>>>>>>>>>>>>> The fact that you need to keep going back to this, and seem to
>>>>>>>>>>>>> just be refusing to accept the conditions under which you have
>>>>>>>>>>>>> proved it just shows the problems with your thought process.
>>>>>>>>>>>>>
>>>>>>>>>>>>>> If H does correctly determine that this is the case in a
>>>>>>>>>>>>>> finite number of steps then H could reject its input on this
>>>>>>>>>>>>>> basis. Here are the details of exactly how H does this in a
>>>>>>>>>>>>>> finite number of steps.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Except that NOW H isn't the H we were just talking about, so
>>>>>>>>>>>>> you are just proving that you are either lying or an idiot.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Remember, the first analysis had the CONDITION on it that H
>>>>>>>>>>>>> did
>>>>>>>>>>>>> a COMPLETE and correct x86 emulation.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Once you remove that property form H, that conclusion no long
>>>>>>>>>>>>> holds and you are shown to be a lying idiot.
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> typedef struct Decoded
>>>>>>>>>>>>>> {
>>>>>>>>>>>>>>     u32 Address;
>>>>>>>>>>>>>>     u32 ESP;          // Current value of ESP
>>>>>>>>>>>>>>     u32 TOS;          // Current value of Top of Stack
>>>>>>>>>>>>>>     u32 NumBytes;
>>>>>>>>>>>>>>     u32 Simplified_Opcode;
>>>>>>>>>>>>>>     u32 Decode_Target;
>>>>>>>>>>>>>> } Decoded_Line_Of_Code;
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>    machine   stack     stack     machine    assembly
>>>>>>>>>>>>>>    address   address   data      code       language
>>>>>>>>>>>>>>    ========  ========  ========  =========  =============
>>>>>>>>>>>>>> [000010d2][00211e8a][00211e8e] 55         push ebp
>>>>>>>>>>>>>> [000010d3][00211e8a][00211e8e] 8bec       mov ebp,esp
>>>>>>>>>>>>>> [000010d5][00211e8a][00211e8e] 8b4508     mov eax,[ebp+08]
>>>>>>>>>>>>>> [000010d8][00211e86][000010d2] 50         push eax        //
>>>>>>>>>>>>>> push P
>>>>>>>>>>>>>> [000010d9][00211e86][000010d2] 8b4d08     mov ecx,[ebp+08]
>>>>>>>>>>>>>> [000010dc][00211e82][000010d2] 51         push ecx        //
>>>>>>>>>>>>>> push P
>>>>>>>>>>>>>> [000010dd][00211e7e][000010e2] e820feffff call 00000f02   //
>>>>>>>>>>>>>> call H
>>>>>>>>>>>>>> Infinitely Recursive Simulation Detected Simulation Stopped
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> // actual fully operational code in the x86utm operating
>>>>>>>>>>>>>> system
>>>>>>>>>>>>>> u32 H(u32 P, u32 I)
>>>>>>>>>>>>>> {
>>>>>>>>>>>>>> HERE:
>>>>>>>>>>>>>>     u32 End_Of_Code;
>>>>>>>>>>>>>>     u32 Address_of_H;              // 2022-06-17
>>>>>>>>>>>>>>     u32 code_end                  = get_code_end(P);
>>>>>>>>>>>>>>     Decoded_Line_Of_Code *decoded = (Decoded_Line_Of_Code*)
>>>>>>>>>>>>>> Allocate(sizeof(Decoded_Line_Of_Code));
>>>>>>>>>>>>>>     Registers*  master_state      = (Registers*)
>>>>>>>>>>>>>> Allocate(sizeof(Registers));
>>>>>>>>>>>>>>     Registers*  slave_state       = (Registers*)
>>>>>>>>>>>>>> Allocate(sizeof(Registers));
>>>>>>>>>>>>>>     u32*        slave_stack       = Allocate(0x10000); //
>>>>>>>>>>>>>> 64k;
>>>>>>>>>>>>>>     u32  execution_trace =
>>>>>>>>>>>>>> (u32)Allocate(sizeof(Decoded_Line_Of_Code) * 1000);
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>     __asm lea eax, HERE             // 2022-06-18
>>>>>>>>>>>>>>     __asm sub eax, 6                // 2022-06-18
>>>>>>>>>>>>>>     __asm mov Address_of_H, eax     // 2022-06-18
>>>>>>>>>>>>>>     __asm mov eax, END_OF_CODE
>>>>>>>>>>>>>>     __asm mov End_Of_Code, eax
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>     Output("Address_of_H:", Address_of_H); // 2022-06-11
>>>>>>>>>>>>>>     Init_slave_state(P, I, End_Of_Code, slave_state,
>>>>>>>>>>>>>> slave_stack);
>>>>>>>>>>>>>>     Output("\nBegin Simulation   Execution Trace Stored at:",
>>>>>>>>>>>>>> execution_trace);
>>>>>>>>>>>>>>     if (Decide_Halting(&execution_trace, &decoded, code_end,
>>>>>>>>>>>>>> &master_state,
>>>>>>>>>>>>>>                        &slave_state, &slave_stack,
>>>>>>>>>>>>>> Address_of_H, P, I))
>>>>>>>>>>>>>>         goto END_OF_CODE;
>>>>>>>>>>>>>>     return 0;  // Does not halt
>>>>>>>>>>>>>> END_OF_CODE:
>>>>>>>>>>>>>>     return 1; // Input has normally terminated
>>>>>>>>>>>>>> }
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> H knows its own machine address and on this basis it can
>>>>>>>>>>>>>> easily examine its stored execution_trace of P and determine:
>>>>>>>>>>>>>> (a) P is calling H with the same arguments that H was called
>>>>>>>>>>>>>> with.
>>>>>>>>>>>>>> (b) No instructions in P could possibly escape this otherwise
>>>>>>>>>>>>>> infinitely recursive emulation.
>>>>>>>>>>>>>> (c) H aborts its emulation of P before its call to H is
>>>>>>>>>>>>>> invoked.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> (b) is NOT a correct rule. Thos has been pointed out before,
>>>>>>>>>>>>> and you have ignored it.
>>>>>>>>>>>>>
>>>>>>>>>>>> That you don't understand what I mean does not mean that it is
>>>>>>>>>>>> an incorrect rule.
>>>>>>>>>>>>
>>>>>>>>>>>> Here is an example where P does have instruction that could
>>>>>>>>>>>> possibly escape this otherwise infinitely recursive emulation:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> void P(ptr x)
>>>>>>>>>>>> {
>>>>>>>>>>>> static count = 0;
>>>>>>>>>>>>     count++;
>>>>>>>>>>>>     if count > 3)
>>>>>>>>>>>>       return;
>>>>>>>>>>>>     if (H(x, x))
>>>>>>>>>>>>       HERE: goto HERE;
>>>>>>>>>>>>     return;
>>>>>>>>>>>> }
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> FALLACY of proof by example. I never said that (b) isn't
>>>>>>>>>>> sometimes true, just it isn't an always true condition. You fail
>>>>>>>>>>> at elementary logic.
>>>>>>>>>>
>>>>>>>>>> Try and find a valid counter-example. Every attempt at rebuttal
>>>>>>>>>> that is not a valid counter-example is one form of deception or
>>>>>>>>>> another.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> P(P)
>>>>>>>>
>>>>>>>> That is not any example of (b), thus another mere strawman
>>>>>>>> deception.
>>>>>>>>
>>>>>>>
>>>>>>> Why not?
>>>>>>>
>>>>>> It is not an example of the simulation of the input to H(P,P) at all.
>>>>>>
>>>>>>
>>>>>
>>>>> Why is P not P?
>>>>>
>>>> It is not a direct rebuttal of my original claim.
>>> And what exactly was your original claim?
>>
>> H is always correct when it determines that an emulated input
>> specifies infinitely nested emulation whenever H matches the (a)(b)(c)
>> criteria to the behavior of this input.
>>
>> Obviously a rebuttal would be to find a case where H is incorrect
>> under these exact same conditions.
>>
>
> No, it doesn't, because what it shows is that a mythological machine was
> correct. The machine described is one that SIMULTANOUSLY does a complete
> and correct emulation of its input, while ALSO stopping in finite time
> to return the non-halting answer.

Because of this reply after I have corrected you hundreds of times I
have blocked you and all of your messages have been erased.

--
Copyright 2022 Pete Olcott

"Talent hits a target no one else can hit;
Genius hits a target no one else can see."
Arthur Schopenhauer

SubjectRepliesAuthor
o Technically competent Software engineers can verify this halting

By: olcott on Wed, 22 Jun 2022

158olcott
server_pubkey.txt

rocksolid light 0.9.81
clearnet tor