[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 kickingvegas):

 FWIW, I'm seeing the same issue. Apparently setting Terminal.app to use
 /opt/local/bin/bash will emit the following message for unknown commands
 entered.

 {{{
 $ jsdf
 objc[53830]: +[__SwiftNativeNSStringBase initialize] may have been in
 progress in another thread when fork() was called.
 objc[53830]: +[__SwiftNativeNSStringBase initialize] may have been in
 progress in another thread when fork() was called. We cannot safely call
 it or ignore it in the fork() child process. Crashing instead. Set a
 breakpoint on objc_initializeAfterForkError to debug.
 Abort trap: 6
 }}}

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