Something has always nagged me about the halting problem, might be my mis-understanding of the problem space but; - You have a piece of software - That software does in memory compute only - The software does not touch any peripherals, networking, or any other external source which introduce unpredictability (x) I'm convinced that somehow this can be solved/proven whether the execution will halt or not. (x) The secon…
For the finite case, the more relevant question is, can you predict whether or not the computation will halt in less time than 1. executing the algorithm and 2. checking whether or not the algorithm ever loops? Bear in mind checking whether or not the algorithm ever loops means taking the full state of the system and checking against a database of all previous states of the system. Bear in mind that the Atari 2600, a…
The approach you describe though is brute force. I don't think (if there even is an answer to this problem) that it can be brute forced; that's where you run into the limits of hardware/computation/energy and start talking about timeframes which exceed the life of the universe.
I think brute force might be a useful tool in places to validate results, but if there _is_ an answer to this problem it's purely mathematical.
Apologies for sounding both excited and naive; these sorts of challenges make me happy in strange ways that no other thing does!