[MacPorts] #68638: bash @5.2.15: When a "command not found" situation happens, Bash prints errors and ends with "Abort Trap: 6" instead of printing "Command not found"

[MacPorts]

#68638: bash @5.2.15: When a "command not found" situation happens, Bash prints
errors and ends with "Abort Trap: 6" instead of printing "Command not
found"
----------------------+----------------------
  Reporter:  some1so  |      Owner:  raimue
      Type:  defect   |     Status:  assigned
  Priority:  Normal   |  Milestone:
 Component:  ports    |    Version:
Resolution:           |   Keywords:
      Port:  bash     |
----------------------+----------------------

Comment (by some1so):

 Hello\\

 I tested this again. I'm using Apple Terminal.app, so I went into settings
 and changed the shell to "/opt/local/bin/bash --noprofile --norc". I then
 created a new window, and tested, and got a good result ("Command not
 found").

 I then renamed my local bash_profile and bashrc files to get them out of
 the way, and set Terminal.app default shell to "/opt/local/bin/bash",
 opened a new window and tested again, and got a bad result (the same Swift
 error).

 Next, I switch Terminal.app default shell to use the system default
 (/bin/bash). Open a new window and test. Good result. I then start a new
 session in the shell by executing "/opt/local/bin/bash", and test again.
 Good result.

 So the only way to cause the error is to set Terminal.app to use
 "/opt/local/bin/bash".

 Maybe of interest - when I am in a session and getting the error, if I use
 "Ctrl-X Ctrl-V" to print the shell version, and then test again, I get a
 good result. Somehow that clears whatever is causing the error.

-- 
Ticket URL: <https://trac.macports.org/ticket/68638#comment:4>
MacPorts <https://www.macports.org/>
Ports system for macOS