@vbabka according to the instructions, you should remove compiled binary before launching it
/me runs
@oleksandr Yes, run, run! That's not what the instructions say. They say: “Don't create a file called that for the test.“ Strictly speaking, once @vbabka ran the gcc command, the instructions can no longer be followed.
/me runs
@oleksandr @vbabka No, I've merely seen too much of this world. I can imagine a QA engineer who writes a workaround which removes the binary in the small race window between execve(2) and open(2). The idea is painfully real.