Re: error message lacks useful debugging information

[Dave Cigna]

I want to thank all of you for taking this issue seriously. I'm sure you 
all agree that when something fails, the error message should provide 
useful information about what went wrong.

If bash simply doesn't have the information because the kernel didn't 
provide it, then perhaps I should throw this to the kernel developers.

I understand that it might not seem like a bug in the usual sense, but I 
hope that you agree that it's something straddling the line between bug 
and "issue" and really is worth fixing. I don't want to get on a 
soapbox, but it's an example of why linux hasn't acquired the share of 
desktop users that it should.

Thank you again for your time.

David Cigna

On 10/5/23 01:04, 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, at least the trivial one i.e the multilib case 
> that seems the most disorientating one, the wrong arch (arm on intel) 
> is already correctly handled, then 'may be' try an ldd (if ldd exist) 
> to mention possible missing libs, all this leading to yet another 
> 'error message' to be entered in the NLS...
>
>
> Or simply a reword of the current implementation
> bash: ./Candle: cannot execute: required file not found
> bash: ./Candle: cannot execute: Possible arch mismatch or missing 
> shared libs
>
> Assuming no QA test already match the "required file not found", if so 
> it would require yet another compat flag...
> With this more explicit error message the OP at least have some clue 
> to of what to look for.