From owner-freebsd-doc@FreeBSD.ORG  Fri Mar  6 13:39:21 2015
Return-Path: <owner-freebsd-doc@FreeBSD.ORG>
Delivered-To: freebsd-doc@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 314D9F11
 for <freebsd-doc@FreeBSD.org>; Fri,  6 Mar 2015 13:39:21 +0000 (UTC)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 16FF7A53
 for <freebsd-doc@FreeBSD.org>; Fri,  6 Mar 2015 13:39:21 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t26DdKct052527
 for <freebsd-doc@FreeBSD.org>; Fri, 6 Mar 2015 13:39:20 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-doc@FreeBSD.org
Subject: [Bug 198216] According to man page for pthread_cond_destroy it
 returns EBUSY error code, but it never does
Date: Fri, 06 Mar 2015 13:39:21 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Documentation
X-Bugzilla-Component: Documentation
X-Bugzilla-Version: Latest
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: jhb@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-doc@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-198216-9-13xEa9vqcM@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-198216-9@https.bugs.freebsd.org/bugzilla/>
References: <bug-198216-9@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-doc@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Documentation project <freebsd-doc.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>,
 <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/>
List-Post: <mailto:freebsd-doc@freebsd.org>
List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>,
 <mailto:freebsd-doc-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Mar 2015 13:39:21 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198216

--- Comment #5 from John Baldwin <jhb@FreeBSD.org> ---
I think warning about double destroys is a feature not a bug though.  Yes, it
is racy, but only for broken applications.  A correctly written application
will never get a spurious error from the EBUSY or is-destroyed checks for
either mutexes or condvars.  A buggy application might get them and might not,
but in the case that it does get them it is helpful.

I put gtk into the buggy application category btw.  It's not just mutexes
either, running any gtk/qt program on the console spews a ton of failed
assertion warnings.  Removing these checks would only make a small dent in the
torrent of messages, but would remove checks that are helpful for other people
who do check errors instead of ignoring them.

-- 
You are receiving this mail because:
You are the assignee for the bug.