[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Misleading error when attempting to run foreign executable
From: |
Alex fxmbsw7 Ratchev |
Subject: |
Re: Misleading error when attempting to run foreign executable |
Date: |
Wed, 13 Oct 2021 16:25:44 +0200 |
also enoexist with its description of the ld parser not available
On Wed, Oct 13, 2021, 16:06 Andrea Monaco <andrea.monaco@autistici.org>
wrote:
>
> > [ENOENT] A component of path or file does not name an existing file
> > or path or file is an empty string.
>
>
> Then ENOENT is clearly not an appropriate error in this case.
>
>
> > [EINVAL] The new process image file has appropriate privileges and
> > has a recognized executable binary format, but the system does not
> > support execution of a file with this format.
>
>
> I think the most fitting is EINVAL, as Robert said. Did someone tell
> the Linux kernel people, so they can fix this? Otherwise I will.
>
>
>
> Andrea Monaco
>
>
- Re: Misleading error when attempting to run foreign executable, (continued)
- Re: Misleading error when attempting to run foreign executable, Robert Elz, 2021/10/11
- Re: Misleading error when attempting to run foreign executable, Chet Ramey, 2021/10/11
- Re: Misleading error when attempting to run foreign executable, Robert Elz, 2021/10/11
- Re: Misleading error when attempting to run foreign executable, Alex fxmbsw7 Ratchev, 2021/10/11
- Re: Misleading error when attempting to run foreign executable, Ángel, 2021/10/12
- Re: Misleading error when attempting to run foreign executable, Eli Schwartz, 2021/10/11
Re: Misleading error when attempting to run foreign executable, Andrea Monaco, 2021/10/13
- Re: Misleading error when attempting to run foreign executable,
Alex fxmbsw7 Ratchev <=