Thread with 11 posts
jump to expanded postRegarding the notion that a program shouldn't crash at all, the argument is there and just in some regards. However, I can edit the memory of any program to crash it. How do you think you could prevent that?
a quote from one of the worst github issue discussions i've seen: https://github.com/official-stockfish/Stockfish/pull/4558
@hikari lol. lmao.
Stop bringing meaningless opinions like "Buffer overflow is a vulnerability"
please excuse me while I go scream into the void for a few hours
@hikari
thanks for sharing the brain damage from this discussion. a whole lot of swearing because someone thinks they're too good to write:
```
if (numberOfMoves == MAX_MOVES)
{
PrintError("Reached move limit.");
ExitCleanly(1);
}
```
or increase a number by 64. computers were a mistake.
@hikari faaaaaark.
Some people should not be permitted to touch a compiler.
Doing wonders for the reputation of chess players' mentality here.
@hikari I had to stop reading. Ow.
I am impressed by the people who managed to keep arguing, in a calm and professional tone, that security bugs are actually bad. It's not an argument you should have to make!
@hikari you think you can crash my program? /joking
main(){}
@hikari I think thereβs an abstraction boundary between βX program in Y language does not crashβ (i.e. in an idealized execution environment) and actual physical realization of execution environments, where you have far fewer ironclad guarantees but still reasonable boundaries and probabilistic evidence that it holds in reasonable circumstances.
@hikari That's not the program crashing. It's a different program, that you produced by modifying the original one, crashing. π