From owner-freebsd-threads@FreeBSD.ORG  Tue Jun 22 21:08:40 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 CB44916A4CF; Tue, 22 Jun 2004 21:08:40 +0000 (GMT)
Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 7DB5643D5A; Tue, 22 Jun 2004 21:08:40 +0000 (GMT)
	(envelope-from dan@dan.emsphone.com)
Received: (from dan@localhost)
	by dan.emsphone.com (8.12.10/8.12.10) id i5ML8L2G051110;
	Tue, 22 Jun 2004 16:08:21 -0500 (CDT)
	(envelope-from dan)
Date: Tue, 22 Jun 2004 16:08:21 -0500
From: Dan Nelson <dnelson@allantgroup.com>
To: Daniel Eischen <eischen@vigrid.com>
Message-ID: <20040622210820.GA17392@dan.emsphone.com>
References: <20040622182632.GJ86471@dan.emsphone.com>
	<Pine.GSO.4.10.10406221614470.17576-100000@pcnet5.pcnet.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.GSO.4.10.10406221614470.17576-100000@pcnet5.pcnet.com>
X-OS: FreeBSD 5.2-CURRENT
X-message-flag: Outlook Error
User-Agent: Mutt/1.5.6i
cc: hackers@freebsd.org
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:08:41 -0000

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.

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

-- 
	Dan Nelson
	dnelson@allantgroup.com