From owner-freebsd-bugs@FreeBSD.ORG Fri Jun 11 07:50:19 2004 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E5D7D16A4D0 for ; Fri, 11 Jun 2004 07:50:19 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id E17E143D31 for ; Fri, 11 Jun 2004 07:50:19 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.11/8.12.11) with ESMTP id i5B7oJTF061874 for ; Fri, 11 Jun 2004 07:50:19 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i5B7oJtM061873; Fri, 11 Jun 2004 07:50:19 GMT (envelope-from gnats) Date: Fri, 11 Jun 2004 07:50:19 GMT Message-Id: <200406110750.i5B7oJtM061873@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Kris Kennaway Subject: Re: kern/67819: libc_r's resolver got broken between 2-Jun-2004 and 9-Jun-2004 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Kris Kennaway List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Jun 2004 07:50:20 -0000 The following reply was made to PR kern/67819; it has been noted by GNATS. From: Kris Kennaway To: "Ralf S.Engelschall" Cc: FreeBSD-gnats-submit@FreeBSD.org Subject: Re: kern/67819: libc_r's resolver got broken between 2-Jun-2004 and 9-Jun-2004 Date: Fri, 11 Jun 2004 00:42:39 -0700 On Fri, Jun 11, 2004 at 08:21:02AM +0200, Ralf S.Engelschall wrote: > >Fix: > I've not investigated what particular MFC between 2-Jun-2004 and > 9-Jun-2004 caused this, but backing out this will certainly fix it > because using the libc_r.so.4 from 2-Jun-2004 fixes the problem > immediately. Sorry, I'm today leaving for holiday so I cannot > investigate myself further, but the problematic MFC should be not too > hard to find as there were not so much MFCs to libc during the mentioned > time range AFAIK. Wasn't this already fixed? Please cvsup again and confirm. Kris