From owner-freebsd-threads@FreeBSD.ORG Mon Feb 2 14:22:48 2004 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4317E16A4CE for ; Mon, 2 Feb 2004 14:22:48 -0800 (PST) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 28B6B43D31 for ; Mon, 2 Feb 2004 14:22:27 -0800 (PST) (envelope-from eischen@vigrid.com) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mail.pcnet.com (8.12.10/8.12.1) with ESMTP id i12MLsiw029327; Mon, 2 Feb 2004 17:21:54 -0500 (EST) Date: Mon, 2 Feb 2004 17:21:54 -0500 (EST) From: Daniel Eischen X-Sender: eischen@pcnet5.pcnet.com To: Craig Rodrigues In-Reply-To: <200402022150.i12LoHq2052250@freefall.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-threads@freebsd.org Subject: Re: bin/35622: sigaltstack is missing in libc_r X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Feb 2004 22:22:48 -0000 On Mon, 2 Feb 2004, Craig Rodrigues wrote: > The following reply was made to PR bin/35622; it has been noted by GNATS. > > From: Craig Rodrigues > To: freebsd-gnats-submit@freebsd.org > Cc: michiel.dewilde@rug.ac.be > Subject: Re: bin/35622: sigaltstack is missing in libc_r > Date: Mon, 2 Feb 2004 16:48:14 -0500 > > Hi, > > In FreeBSD-CURRENT, libc_r does not have a symbol > for sigaltstack which overrides the symbol in libc. libc_r was built around the 96 POSIX spec that said that use of sigaltstack in a threaded program was undefined. > However, the new libpthread does have such a symbol. The new 200x POXIC spec allows sigaltstack() so David added it to libpthread. It is mostly for threads bound to kernel scheduleable entities, and use of it otherwise is undefined. Don't tell anyone, but libpthread does allow it even for scope process threads.