From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 18 15:53:56 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 17CEB37B401; Fri, 18 Apr 2003 15:53:56 -0700 (PDT) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5D02C43FA3; Fri, 18 Apr 2003 15:53:55 -0700 (PDT) (envelope-from eischen@pcnet1.pcnet.com) Received: from pcnet1.pcnet.com (localhost [127.0.0.1]) by mail.pcnet.com (8.12.8/8.12.1) with ESMTP id h3IMrsBg005358; Fri, 18 Apr 2003 18:53:54 -0400 (EDT) Received: from localhost (eischen@localhost)h3IMrsnO005354; Fri, 18 Apr 2003 18:53:54 -0400 (EDT) Date: Fri, 18 Apr 2003 18:53:54 -0400 (EDT) From: Daniel Eischen To: Alex Semenyaka In-Reply-To: <20030418224522.GA63339@snark.ratmir.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-hackers@freebsd.org cc: David Xu cc: freebsd-threads@freebsd.org Subject: Re: libpthread patch X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Apr 2003 22:53:56 -0000 On Sat, 19 Apr 2003, Alex Semenyaka wrote: > On Wed, Apr 16, 2003 at 01:09:46PM -0400, Daniel Eischen wrote: > > Found it! The library's version of sigaction was not allowing > > a signal handler for SIGCHLD to be installed; it was leftover > > from libc_r. > > By the way, in this connection could somebody check my follow-up to > the PR bin/48856? I suggested a really small fix (3 lines in total) > to the current implementation of the signal(). With the current one > the call of signal(SIGCHLD, SIG_IGN) still allows zombie to be born. > There are to places to fix actually, one is the standard libc and > second is the pthreads (that's why I am sending this message to > -threads as well). If that fix is bad somehow I would gladly receive > any explanations. Thanks! I don't think you can always set SA_NOCLDWAIT because it could screw up wait() in programs that don't set SA_NOCLDWAIT. -- Dan Eischen