This reminds me of a bug in macOS that for a while caused our builds to fail once or twice a month with something like "/bin/sh: /bin/sh: cannot execute binary

This reminds me of a bug in macOS that for a while caused our builds to fail once or twice a month with something like "/bin/sh: /bin/sh: cannot execute binary file" This was because sometimes, the kernel would fail to execute a binary for some reason (this was the core bug), returning ENOEXEC to the libc, which, dutifully, would pass it on to the shell as documented in the article. Of course since the failed executable was a real binary, not a script, the shell would fail with the above error. I haven't encountered the bug in a couple years, so I guess they finally fixed it. Silently.