bash prints errors for every non-existing command

[brian]

Bash should probably be compiled with --disable-nls to workaround.

More generally this problem is described here:
http://sealiesoftware.com/blog/archive/2017/6/5/Objective-C_and_fork_in_macOS_1013.html
and here: https://wefearchange.org/2018/11/forkmacos.rst.html and here:
https://blog.phusion.nl/2017/10/13/why-ruby-app-servers-break-on-macos-high-sierra-and-what-can-be-done-about-it/

It's not a gettext issue. It's just like calling malloc in a signal
handler. Or backtrace to catch that SIGSEGV if you aren't careful. LOL.

Thanks.

On Thu, Apr 25, 2024 at 2:08 AM Baerenblau via macports-users <
macports-users at lists.macports.org> wrote:

> Indeed, $LANG is the root cause (any of $LC_* is not set). Unset of $LANG
> or LANG=en_US.UTF-8 helps in my environment, setting it to e.g. "C" does
> not help.
>
> At least a workaround :-)
>
> Issue #41248 was created 10 years ago but it didn't happen for me until I
> upgraded to the current or previous Macos version.
>
> Thanks!
>
> Am 24.04.24 um 23:42 schrieb Rainer Müller:
> > On 24.04.24 18:33, Baerenblau via macports-users wrote:
> >> I'm on macOS 14.4.1 (23E224) and continue to experience a long standing
> problem with bash from Macports
> >>
> >> % which bash
> >> /opt/local/bin/bash
> >>
> >> % bash --version
> >> GNU bash, Version 5.2.26(1)-release (x86_64-apple-darwin23.2.0)
> >>
> >> For every command which is not found a error similar error like this is
> printed:
> >>
> >> $ asdf
> >> objc[1321]: +[__SwiftNativeNSStringBase initialize] may have been in
> progress in another thread when fork() was called.
> >> objc[1321]: +[__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
> >>
> >> Xcode has been installed today. Then MacPorts has been updated to the
> latest version, machine is rebooted, issue continues to exist.
> >
> > This is indeed a very long standing issue:
> > https://trac.macports.org/ticket/41248
> > https://trac.macports.org/ticket/68638
> >
> > It appears that this crash is actually caused by gettext, when
> localizing the error message in the child process forked by bash.
> >
> > Rainer
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-users/attachments/20240425/fbbd3c22/attachment.htm>