Date: Wed, 21 Oct 1998 14:07:56 -0700 (PDT) From: Archie Cobbs <archie@whistle.com> To: eischen@vigrid.com (Daniel Eischen) Cc: eischen@vigrid.com, lists@tar.com, current@FreeBSD.ORG Subject: Re: Another Serious libc_r problem Message-ID: <199810212107.OAA28265@bubba.whistle.com> In-Reply-To: <199810211519.LAA07958@pcnet1.pcnet.com> from Daniel Eischen at "Oct 21, 98 11:19:01 am"
next in thread | previous in thread | raw e-mail | index | archive | help
Daniel Eischen writes: > the mutex, and then your solution works. If it doesn't own > the mutex, then you've got a potential deadlock condition, > but this could be deemed acceptable because POSIX says that > "undefined behavior" will occur in this case. Random interjected comment.. I would argue that for any case that POSIX says results in "undefined behavior", and the pthread code can easily detect this case, FreeBSD should immediately abort(3). Threads programmers will thank you when their bugs are revealed for them. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199810212107.OAA28265>