Date: Fri, 06 Mar 2015 13:39:21 +0000 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 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/>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-198216-9-13xEa9vqcM>