From owner-freebsd-threads@FreeBSD.ORG Fri Apr 15 15:00:05 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 9EA1B16A4CE for ; Fri, 15 Apr 2005 15:00:05 +0000 (GMT) Received: from mxsf41.cluster1.charter.net (mxsf41.cluster1.charter.net [209.225.28.173]) by mx1.FreeBSD.org (Postfix) with ESMTP id 06A9043D1F for ; Fri, 15 Apr 2005 15:00:05 +0000 (GMT) (envelope-from archie@dellroad.org) Received: from mxip07.cluster1.charter.net (mxip07a.cluster1.charter.net [209.225.28.137])j3FF03bb019924 for ; Fri, 15 Apr 2005 11:00:03 -0400 Received: from cable-68-113-94-164.mtv.al.charter.com (HELO InterJet.dellroad.org) (68.113.94.164) by mxip07.cluster1.charter.net with ESMTP; 15 Apr 2005 11:00:03 -0400 X-Ironport-AV: i="3.92,105,1112587200"; d="scan'208"; a="856074270:sNHT18644772" Received: from arch20m.dellroad.org (arch20m.dellroad.org [10.2.2.20]) by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id JAA14001 for ; Fri, 15 Apr 2005 09:52:24 -0500 (CDT) Received: from [127.0.0.1] (localhost [127.0.0.1])j3FEqNBe007168 for ; Fri, 15 Apr 2005 09:52:24 -0500 (CDT) (envelope-from archie@dellroad.org) Message-ID: <425FD527.1000102@dellroad.org> Date: Fri, 15 Apr 2005 09:52:23 -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: freebsd-threads@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: 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: Fri, 15 Apr 2005 15:00:05 -0000 On FreeBSD 4.9 I'm seeing a bug where pthread_getspecific() sometimes returns the wrong value when invoked from within a signal handler. ISTR this bug was fixed in a later version of FreeBSD. However, I can't seem to find any reference to the bug, any information about when it was fixed, etc. (FreeBSD's mailing list search ability doesn't help much). If anyone knows any more details about this bug I'd appreciate knowing any more details. Thanks, -Archie __________________________________________________________________________ Archie Cobbs * CTO, Awarix * http://www.awarix.com