Date: Fri, 08 Mar 2019 21:07:37 +0000 From: bugzilla-noreply@freebsd.org To: threads@FreeBSD.org Subject: [Bug 234805] pthread_*_destroy doesn't handle locked objects consistently Message-ID: <bug-234805-13406-zPVO9U5utV@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-234805-13406@https.bugs.freebsd.org/bugzilla/> References: <bug-234805-13406@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D234805 --- Comment #7 from commit-hook@freebsd.org --- A commit references this bug: Author: markj Date: Fri Mar 8 21:07:09 UTC 2019 New revision: 344935 URL: https://svnweb.freebsd.org/changeset/base/344935 Log: Have pthread_cond_destroy() return EBUSY if the condvar has waiters. This is not required of a compliant implementation, but it's easy to check for and helps improve compatibility with other common implementations. Moreover, it's consistent with our pthread_mutex_destroy(). PR: 234805 Reviewed by: jhb, kib, ngie MFC after: 2 weeks Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D19496 Changes: head/contrib/netbsd-tests/lib/libpthread/t_cond.c head/lib/libthr/thread/thr_cond.c --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-234805-13406-zPVO9U5utV>