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

[Tom]

> Oh, I see, from gettext-0.22.

Yes, that's right, this came up in the context of a [macports bug report][1].

> Still, how should bash avoid this using only public function interfaces?

That report has a work-around invoking a syntax error which presumably calls 
out to `setlocale`/`gettext` pre-`fork`, caching the result somewhere (`bash` 
or `gettext`?) such that the offending call post-`fork` on an unknown command 
doesn't trigger this issue.

That feels brittle; a more general approach might be to move both invocations 
either side of the fork (as alluded to by the [gettext maintainer][2]), which 
for `bash` probably means calling `gettext` before `fork`.

[1]: https://trac.macports.org/ticket/68638
[2]: https://lists.gnu.org/archive/html/bug-gettext/2024-05/msg00001.html