Re: error message lacks useful debugging information

[Phi Debian]

On Thu, Oct 5, 2023 at 12:57 PM Greg Wooledge <greg@wooledge.org> wrote:

> On Thu, Oct 05, 2023 at 07:04:26AM +0200, Phi Debian wrote:
> > Since we are on the error path (not the perf path) may be the shell could
> > go the extra miles and try some more diag, has it does for shebang, on
> > ENOENT, the shell could try to open the a.out, if OK try some other
> > euristics, [...]
>
> Just for the record, trying to open the program for reading is only
> possible for scripts.  It's not too uncommon for a compiled program
> to have +x permission for the user, but *not* +r permission.  Such a
> program can be executed, but not opened for reading.
>
>
Correct, this is why I proposed the later case, when the shell can not find
out more to say, just do nothing and simply  suggest some known cases of
trouble, yet if the shell can provide more insight, run file(1) and/or an
ldd(1) could be usefull. This is the counter part for an interpreter of
what compiler do, long time ago, diag from various compiler where very
limited, and nowaday they try to be as accurate as possible.