Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -g -O2 -fdebug-prefix-map=/build/bash-Smvct5/bash-5.0=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wno-parentheses -Wno-format-security uname output: Linux ip-172-31-20-239 5.13.0-1021-aws #23~20.04.2-Ubuntu SMP Thu Mar 31 11:36:15 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Machine Type: x86_64-pc-linux-gnu

Bash Version: 5.0
Patch Level: 17
Release Status: release

Description:
         When a user attempts to execute an executable that is not recognized as an executable by the system, the generated error is "No such file or directory"

Repeat-By:
         Obtain an i386 executable instead of an amd64 executable and attempt to run it via ./name_of_executable

Fix:
         If the file exists but cannot be executed, issue an error message that is not so misleading. The file does exist, so "No such file or directory" seems plain wrong.
  • Unfortunate er... AA via Bug reports for the GNU Bourne Again SHell
    • Re: Unfor... Chet Ramey
      • Re: U... Dale R. Worley
        • R... AA via Bug reports for the GNU Bourne Again SHell
          • ... Dale R. Worley
            • ... Andrew Athan via Bug reports for the GNU Bourne Again SHell
              • ... Chet Ramey
          • ... Martin D Kealey
            • ... Andrew Athan via Bug reports for the GNU Bourne Again SHell
              • ... AA via Bug reports for the GNU Bourne Again SHell
                • ... Chet Ramey

Reply via email to