From owner-freebsd-current Mon Sep 14 05:35:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA27919 for freebsd-current-outgoing; Mon, 14 Sep 1998 05:35:37 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA27914 for ; Mon, 14 Sep 1998 05:35:35 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id IAA22968; Mon, 14 Sep 1998 08:35:20 -0400 (EDT) Date: Mon, 14 Sep 1998 08:35:20 -0400 (EDT) From: Daniel Eischen Message-Id: <199809141235.IAA22968@pcnet1.pcnet.com> To: eischen@vigrid.com, jb@cimlogic.com.au Subject: Re: Pthreads fixes before 3.0 release Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The patch you posted breaks pause(). I committed the patch, but had > to back it out later when I found the breakage. I hope to have time > to sort out the problem before 3.0 goes out the door. No, this is a second patch. It fixes the problem with sigsuspend (sigpause). I saw the commit messages when you added my first patch and then when you backed it out. I went back and fixed it, and added another test program to verify sigsuspend. Basically, the patch adds another state so that sigwait and sigsuspend are placed in unique states. See kern/7586 for details. > Unfortunately we each don't use all the functions in the library, so > it is possible to apply a "fix" to one that breaks another. This is > why I started committing the test programs that people provide. All > my tests run under a proprietary build-test-release system that is very > un-BSD so there is no point releasing the code. If something breaks let me know. I am willing to track down any problems associated with this patch - I don't necessarily need your test programs, just a description of what broke. I know you've been busy being Elf-man, which is why I didn't mail you directly regarding this. Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message