From owner-freebsd-threads@FreeBSD.ORG  Mon Apr 18 18:23:01 2005
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 C650316A4CE; Mon, 18 Apr 2005 18:23:01 +0000 (GMT)
Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 359D543D3F; Mon, 18 Apr 2005 18:23:01 +0000 (GMT)
	(envelope-from deischen@freebsd.org)
Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11])
	j3IIMxVU026439;	Mon, 18 Apr 2005 14:22:59 -0400 (EDT)
Date: Mon, 18 Apr 2005 14:22:59 -0400 (EDT)
From: Daniel Eischen <deischen@freebsd.org>
X-X-Sender: eischen@sea.ntplx.net
To: Archie Cobbs <archie@dellroad.org>
In-Reply-To: <4263F952.1000106@dellroad.org>
Message-ID: <Pine.GSO.4.43.0504181417400.58-100000@sea.ntplx.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net)
cc: David Xu <davidxu@freebsd.org>
cc: freebsd-threads@freebsd.org
Subject: Re: Bug with pthread_getspecific() and signals
X-BeenThere: freebsd-threads@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: Daniel Eischen <deischen@freebsd.org>
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: Mon, 18 Apr 2005 18:23:01 -0000

On Mon, 18 Apr 2005, Archie Cobbs wrote:

> Daniel Eischen wrote:
> >>If it does, can you show me in which FreeBSD releases the bug is fixed?
> >
> > I don't know if it ever got fixed in libc_r.
> >
> > ...
> >
> > It should work correctly in both libpthread and libthr.
> > libc_r is not being maintained.
>
> Thanks.. unfortunately I'm not familiar with the exact history of
> FreeBSD's thread libraries.
>
> Can you help me understand how to detect/workaround this problem in my
> configure script?
>
> E.g., I need to know:
>
> - In what versions of FreeBSD will "-pthread" result in a non-broken
>    (with respect to this bug) thread library?

Probably when -pthread was switched to libpthread from libc_r.
Search the CVS commit log for sys/sys/param.h (r1.178).

> - Of the earlier versions of FreeBSD, in which ones is there a viable
>    workaround and what is it (e.g., "-lpthread" instead of "-pthread"?)

Probably not until 5.3-Release where libpthread became the default.

> This bug makes my application basically useless so it's critical to
> understand when and how I can work around it. I'd like to add logic
> to the configure script to determine either (a) to give up, or (b)
> what the appropriate linker flag is, given the version of FreeBSD.

-- 
DE