From owner-freebsd-threads@FreeBSD.ORG  Tue Jun 22 21:50:53 2004
Return-Path: <owner-freebsd-threads@FreeBSD.ORG>
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 8E11316A4CE
	for <threads@freebsd.org>; Tue, 22 Jun 2004 21:50:53 +0000 (GMT)
Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 2F93643D2D
	for <threads@freebsd.org>; Tue, 22 Jun 2004 21:50:53 +0000 (GMT)
	(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 i5MLoYon005443;
	Tue, 22 Jun 2004 17:50:34 -0400 (EDT)
Date: Tue, 22 Jun 2004 17:50:34 -0400 (EDT)
From: Daniel Eischen <eischen@vigrid.com>
X-Sender: eischen@pcnet5.pcnet.com
To: Dan Nelson <dnelson@allantgroup.com>
In-Reply-To: <20040622210820.GA17392@dan.emsphone.com>
Message-ID: <Pine.GSO.4.10.10406221745060.4146-100000@pcnet5.pcnet.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: threads@freebsd.org
cc: Chris Stenton <jacs@gnome.co.uk>
Subject: Re: pthread - fork - execv problem
X-BeenThere: freebsd-threads@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Threading on FreeBSD <freebsd-threads.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
	<mailto:freebsd-threads-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-threads>
List-Post: <mailto:freebsd-threads@freebsd.org>
List-Help: <mailto:freebsd-threads-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
	<mailto:freebsd-threads-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Jun 2004 21:50:53 -0000

On Tue, 22 Jun 2004, Dan Nelson wrote:

> In the last episode (Jun 22), Daniel Eischen said:
> > > libpthread in -current does support pthread_atfork, and I have a
> > > patch (below) that adds the same functionality to libc_r and libthr
> > > that I need to send-pr.  Pointy hat to the original committer for
> > > breaking ABI compatibility.  http://dan.allantgroup.com/FreeBSD/
> > 
> > Whaa?  Adding a function doesn't break ABI, and I don't want to
> > maintain 3 thread libraries.
> 
> It does if an application detects pthread_fork during configure and
> uses it.  You then can't use libmap to redirect libpthread to one of
> the other thread libraries for testing, since you'll get an undefined
> symbol error at runtime.

Bah.  libc_r is marked for deprecation and libpthread is the
default library in -current.

> Nikos Ntarmos also noticed that there's no pthread_atfork manpage.  We
> could probably just use the Single Unix one.

Yes, you can now that The Open Group have given us permission :-)

-- 
Dan Eischen