Date: Wed, 4 Jun 2003 09:59:10 -0700 (PDT) From: Julian Elischer <julian@elischer.org> To: Kern Sibbald <kern@sibbald.com> Cc: freebsd-threads@freebsd.org Subject: Re: FreeBSD pthread_equal "bug" Message-ID: <Pine.BSF.4.21.0306040951450.80038-100000@InterJet.elischer.org> In-Reply-To: <1054745115.13630.517.camel@rufus>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4 Jun 2003, Kern Sibbald wrote: > > that's a bonus ;-) > > This bug does not highlight bad applications because most > programmers will reasonably expect that pthread_equal() will > not be the same for two different threads. It took me > a long time to find this problem because I just could not > imagine that pthread_equal() was not "working". > This problem is extremely subtle and is likely to cause > unsuspecting applications long months of bizarre > behavior. If IDs are recycled after a LONG time then there is still a chance that the test could go the wrong way if something held up the tester for a long enough time, so the behaviour is not "perfect", > > Fix it or not, that is your choice. Now that I know > that you don't handle it as I would suspect I can code > around it. best for now.. it is now on our radar anyhow.. thanks... > > _______________________________________________ > freebsd-threads@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-threads > To unsubscribe, send any mail to "freebsd-threads-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0306040951450.80038-100000>