[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.BSM.4.64L.2407240005160.16013@herc.mirbsd.org>
Date: Wed, 24 Jul 2024 00:11:28 +0000 (UTC)
From: Thorsten Glaser <tg@...bsd.de>
To: musl@...ts.openwall.com
Subject: Re: Maybe A Bug about timer_create and pthread_barrier_wait
Rich Felker dixit:
>There's an old unverified suspicion that our pthread barrier
>implementation has serious flaws. Unfortunately I hadn't gotten around
From having looked at the documentation and the OP’s description
of their understanding of the issue (I don’t understand enough of
the actual code), I got the idea that maybe the musl implementation
accesses the pthread_barrier_t object after at least one of the
threads has returned (which can lead to freeing the object by the
caller). I don’t know enough about parallel programming to be any
more help in debugging that though, or even in checking whether
that’s indeed the case.
bye,
//mirabilos
--
<igli> exceptions: a truly awful implementation of quite a nice idea.
<igli> just about the worst way you could do something like that, afaic.
<igli> it's like anti-design. <mirabilos> that too… may I quote you on that?
<igli> sure, tho i doubt anyone will listen ;)
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
