Date: Sun, 29 Jun 2003 08:43:37 -0700 (PDT) From: John Polstra <jdp@polstra.com> To: current@freebsd.org Subject: Re: HEADS UP: libthr broken (was Re: HEADS UP: new KSE signal code) Message-ID: <200306291543.h5TFhb8V050180@strings.polstra.com> In-Reply-To: <20030628220022.QXMV3199.pop016.verizon.net@kokeb.ambesa.net> References: <Pine.BSF.4.21.0306281219320.2537-100000@InterJet.elischer.org> <890E3745-A9A3-11D7-B882-0003937E39E0@mac.com> <20030628201814.GA33532@HAL9000.homeunix.com> <20030628220022.QXMV3199.pop016.verizon.net@kokeb.ambesa.net>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <20030628220022.QXMV3199.pop016.verizon.net@kokeb.ambesa.net>, Mike Makonnen <mtm@identd.net> wrote: > David's signal changes broke libthr. This is not his fault. The > original implementation of sigtimedwait was broken and jdp (John > Polstra) had worked up patches to fix it, but David beat him to it > :-). Well, it would have been nice if David had done a findgrep over the source tree to see if any existing code relied on the broken semantics of the original sigtimedwait implementation. > Libthr depended on the old "broken" semantics of sigtimedwait, so > any applications using libthr will be broken untill jdp commits the > second part of his patch. OK, I'm working on it ... John -- John Polstra John D. Polstra & Co., Inc. Seattle, Washington USA "Two buttocks cannot avoid friction." -- Malawi saying
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200306291543.h5TFhb8V050180>