Date: Tue, 22 Mar 2016 17:27:49 +0200 From: Konstantin Belousov <kostikbel@gmail.com> To: Benjamin Kaduk <bjkfbsd@gmail.com> Cc: "src-committers@freebsd.org" <src-committers@freebsd.org>, "svn-src-all@freebsd.org" <svn-src-all@freebsd.org>, "svn-src-head@freebsd.org" <svn-src-head@freebsd.org> Subject: Re: svn commit: r297185 - head/lib/libthr/thread Message-ID: <20160322152749.GT1741@kib.kiev.ua> In-Reply-To: <CAJ5_RoBu0pP%2B3S9gUkkEj2-oiay%2BF0KN2u=h3rMCFKbQUJx_6w@mail.gmail.com> References: <201603221051.u2MAphFa074523@repo.freebsd.org> <CAJ5_RoBu0pP%2B3S9gUkkEj2-oiay%2BF0KN2u=h3rMCFKbQUJx_6w@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Mar 22, 2016 at 09:25:48AM -0500, Benjamin Kaduk wrote: > On Tue, Mar 22, 2016 at 5:51 AM, Konstantin Belousov <kib@freebsd.org> > wrote: > > > Author: kib > > Date: Tue Mar 22 10:51:42 2016 > > New Revision: 297185 > > URL: https://svnweb.freebsd.org/changeset/base/297185 > > > > Log: > > Apparently there are some popular programs around which assume that it > > is safe to call pthread_mutex_init() on the same shared mutex several > > times. POSIX claims that the behaviour in this case is undefined. > > > > Has anyone volunteered to tell KDE they're doing it wrong? (Do we know of > anything other than KDE?) I am not aware is the answer to both your questions. For useful report to KDE people, somebody should at least do some debugging on KDE side. E.g., what is the lock which was initialized twice, and how does it happen ? I looked at the issue from the internal side of the libthr, and have no energy to read and understand KDE code.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160322152749.GT1741>