From owner-freebsd-threads@FreeBSD.ORG Mon Apr 18 18:15:55 2005 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 4903316A4DD for ; Mon, 18 Apr 2005 18:15:55 +0000 (GMT) Received: from zixvpm01.stv.org (zixvpm01.stv.org [207.203.41.67]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF59343D1D for ; Mon, 18 Apr 2005 18:15:54 +0000 (GMT) (envelope-from archie@dellroad.org) Received: from zixvpm01.stv.org (ZixVPM [127.0.0.1]) by Outbound.stv.org (Proprietary) with ESMTP id A52F01301A9 for ; Mon, 18 Apr 2005 13:15:26 -0500 (CDT) Received: from STVAVAPPL1.BHMSTV (unknown [10.104.14.2]) by zixvpm01.stv.org (Proprietary) with SMTP id 662F3190004; Mon, 18 Apr 2005 13:15:25 -0500 (CDT) Received: from unknown(10.104.145.22) by STVAVAPPL1.BHMSTV via csmap id 40f5ed4a_b033_11d9_8eeb_00304811e8c8_1771; Mon, 18 Apr 2005 12:56:56 -0500 (CDT) Received: from [127.0.0.1] (localhost [127.0.0.1])j3IIFk5K000542; Mon, 18 Apr 2005 13:15:47 -0500 (CDT) (envelope-from archie@dellroad.org) Message-ID: <4263F952.1000106@dellroad.org> Date: Mon, 18 Apr 2005 13:15:46 -0500 From: Archie Cobbs User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.3) Gecko/20041129 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel Eischen References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: David Xu 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 List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Apr 2005 18:15:55 -0000 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? - Of the earlier versions of FreeBSD, in which ones is there a viable workaround and what is it (e.g., "-lpthread" instead of "-pthread"?) 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. Thanks, -Archie __________________________________________________________________________ Archie Cobbs * CTO, Awarix * http://www.awarix.com