Halting problem proofs refuted on the basis of software engineering

What is the basis for reason? And mathematics?

Moderators: AMod, iMod

Post Reply
PeteOlcott
Posts: 1514
Joined: Mon Jul 25, 2016 6:55 pm

Halting problem proofs refuted on the basis of software engineering

Post by PeteOlcott »

This much more concise version of my paper focuses on the actual
execution of three fully operational examples.

H0 correctly determines that Infinite_Loop() never halts
H correctly determines that Infinite_Recursion() never halts
H correctly determines that P() never halts

void P(u32 x)
{
if (H(x, x))
HERE: goto HERE;
return;
}

int main()
{
Output("Input_Halts = ", H((u32)P, (u32)P));
}

As shown below the above P and H have the required (halting problem) pathological relationship to each other:
For any program H that might determine if programs halt, a "pathological"
program P, called with some input, can pass its own source and its input to
H and then specifically do the opposite of what H predicts P will do. No H
can exist that handles this case. https://en.wikipedia.org/wiki/Halting_problem
I really need software engineers to verify that H does correctly predict that its complete and correct x86 emulation of its input would never reach the "ret" instruction of this input.

Halting problem proofs refuted on the basis of software engineering
https://www.researchgate.net/publicatio ... ngineering
Post Reply