On 22/10/2019 03:13, Michael Coleman via GNU coreutils Bug Reports wrote:
One of my users unwittingly stumbled upon the most delightful 'env' bug. It
seems to be present in a couple of pretty recent distributions.
Try this:
----------------------------
#!/usr/bin/env
whatever
----------------------------
This results in an endless 'execve' recursion (if that's the word), pegging the
CPU.
The preferred behavior would be something like a diagnostic, followed by
immediate exit with an error result.
Well env is being passed the script name again as an option by the kernel,
and is just executing that. There is no portable way I can see for env
to distinguish this case. I'm not sure it's such an important issue TBH.
cheers,
Pádraig
