[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Less detailed error for ENOENT from execve
|
From: |
Chet Ramey |
|
Subject: |
Re: Less detailed error for ENOENT from execve |
|
Date: |
Mon, 10 Oct 2022 15:19:47 -0400 |
|
User-agent: |
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.3.1 |
On 10/9/22 11:32 AM, Kirill Elagin wrote:
Hi,
I think the execute_cmd.c change here
(https://git.savannah.gnu.org/cgit/bash.git/commit/?h=devel&id=1fff64acdc5709cdc213f0143f1b8169fdf68a39)
made things worse, not better. I don’t know what the original report
that prompted this change was though, but my impression is that the
error became much less detailed.
I see what you mean. The function should check for the interpreter case
before printing the generic ENOENT message. I'll make that change.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU chet@case.edu http://tiswww.cwru.edu/~chet/