bash prints errors for every non-existing command

Baerenblau baerenblau at yahoo.de
Thu Apr 25 06:08:06 UTC 2024


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


More information about the macports-users mailing list