bug-bash
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: macOS 14 objc `+initialize` forced crash due to fork after thread


From: Chet Ramey
Subject: Re: macOS 14 objc `+initialize` forced crash due to fork after thread
Date: Thu, 2 May 2024 10:54:52 -0400
User-agent: Mozilla Thunderbird

On 5/2/24 2:23 AM, Tom wrote:

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

Description:

When linked against `libintl.8.dylib`, if an unknown comand is executed, the
following error is seen:

Where do you get libintl.8.dylib? I don't see it on my macOS systems.

And doesn't this look like a problem internal to libintl? Bash is using
public APIs: setlocale(), gettext(), etc. How should it avoid this?

(I note that this doesn't happen when bash links with the libintl from
gnulib that is included in the distribution.)

Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
                 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]