degraded error message in case of hash-bang interpreter error

[H.Janssen]

Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -O2 -flto=auto -ffat-lto-objects -fexceptions -g 
-grecord-gcc-switches -pipe -Wall -Werror=format-security 
-Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS 
-specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong 
-specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -mtune=generic 
-fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection
uname output: Linux lap2.home 6.0.9-300.fc37.x86_64 #1 SMP 
PREEMPT_DYNAMIC Wed Nov 16 17:36:22 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Machine Type: x86_64-redhat-linux-gnu

Bash Version: 5.2
Patch Level: 9
Release Status: release

Description:
   If the interpreter after #! is wrong, a non-informative message is 
printed

Repeat-By:
    "unix2dos bashscript" starting with #!/bin/bash
    ./bashscript
     bash: ./bashscript: cannot execute: required file not found

         Before version 5.2:
    ./bashscript
    bash: ./bashscript: /bin/bash^M: bad interpreter: No such file or 
directory

Fix:
    Probably some code has to be moved in execute_cmd.c

Thanks a lot!


--
H.Janssen
Lekerwaard 36
1824HC Alkmaar
06-58971047