From owner-freebsd-current Wed Oct 21 14:33:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA14502 for freebsd-current-outgoing; Wed, 21 Oct 1998 14:33:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from porkfriedrice.ny.genx.net (porkfriedrice.ny.genx.net [206.64.4.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA14489 for ; Wed, 21 Oct 1998 14:33:22 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by porkfriedrice.ny.genx.net (8.9.1/8.9.1) with ESMTP id RAA01626; Wed, 21 Oct 1998 17:35:07 -0400 (EDT) (envelope-from bright@hotjobs.com) X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs Date: Wed, 21 Oct 1998 17:35:07 -0400 (EDT) From: Alfred Perlstein X-Sender: bright@porkfriedrice.ny.genx.net To: Daniel Eischen cc: current@FreeBSD.ORG Subject: Re: Another Serious libc_r problem In-Reply-To: <199810212121.RAA16655@pcnet1.pcnet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG while we're on the subject, does anyone know the defined behavior when a threaded process fork()s? i can't seem to find anything in the small library of stevens books i've been collecting over the past couple of years. Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current On Wed, 21 Oct 1998, Daniel Eischen wrote: > > 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. > > If it's like pthread_mutex_lock(), POSIX will say that pthread_cond_wait > should return EINVAL if it doesn't own the mutex *and* this condition > is detected by the implementation. Much as we'd like to say "Bad > programmer, Bad!" I don't think POSIX will allow us to with anything > other than an EINVAL return value. > > Dan Eischen > eischen@vigrid.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message