On Mon, Mar 03, 2025 at 06:08:17PM +0000, Taylor R Campbell wrote:
> > Please everyone, avoid implementing hasty solutions, just because we
> > seem to need a solution to something today - we don't - a few days more
> > consideration and discussion can make solutions much more sane, and less
> > likely to cause problems.
>
> I think it is a trifle excessive to characterize a never-fails variant
> of pthread_atfork with caller-allocated storage as insane.
>
> But since this change is evidently controversial, which I hadn't
> anticipated when I committed it, I'll revert it for now.
As far as I can tell there was something genuinely broken in your
implementation. I encountered mutex panics in the Perl interpreter
(taken from "pkgsrc/lang/perl5") under a freshly built NetBSD-current
for amd64 yesterday. An easy way to reproduce them was to try to
build "pkgsrc/lang/perl5".
After rebuilding and installing "libc" and "libpthread" from today's
NetBSD-current sources Perl works fine again.
Kind regards
--
Matthias Scheler https://zhadum.org.uk/
