From owner-freebsd-current@FreeBSD.ORG Mon Oct 15 14:08:34 2007 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 628C116A417 for ; Mon, 15 Oct 2007 14:08:34 +0000 (UTC) (envelope-from rermilov@team.vega.ru) Received: from mail.vega.ru (mx1.vega.ru [87.242.77.163]) by mx1.freebsd.org (Postfix) with ESMTP id 200C113C474 for ; Mon, 15 Oct 2007 14:08:33 +0000 (UTC) (envelope-from rermilov@team.vega.ru) Received: from [87.242.97.68] (port=56655 helo=edoofus.dev.vega.ru) by mail.vega.ru with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68 (FreeBSD)) (envelope-from ) id 1IhQcJ-000H7o-Q4; Mon, 15 Oct 2007 14:08:23 +0000 Received: from edoofus.dev.vega.ru (localhost [127.0.0.1]) by edoofus.dev.vega.ru (8.14.1/8.14.1) with ESMTP id l9FE7aBw078661; Mon, 15 Oct 2007 18:07:36 +0400 (MSD) (envelope-from rermilov@team.vega.ru) Received: (from ru@localhost) by edoofus.dev.vega.ru (8.14.1/8.14.1/Submit) id l9FE7aSH078660; Mon, 15 Oct 2007 18:07:36 +0400 (MSD) (envelope-from rermilov@team.vega.ru) X-Authentication-Warning: edoofus.dev.vega.ru: ru set sender to rermilov@team.vega.ru using -f Date: Mon, 15 Oct 2007 18:07:36 +0400 From: Ruslan Ermilov To: sklarkin Message-ID: <20071015140736.GA3974@team.vega.ru> References: <5b150c9c0710150645h37b2a647u1eae0896941b2601@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5b150c9c0710150645h37b2a647u1eae0896941b2601@mail.gmail.com> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-current@FreeBSD.org Subject: Re: error with thread X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Oct 2007 14:08:34 -0000 On Mon, Oct 15, 2007 at 05:45:51PM +0400, sklarkin wrote: > Daniel Eischen wrote: > > On Mon, 15 Oct 2007, oleg palukhin wrote: > > > >> hi, list > >> > >> on recently builded -current when i start X, portupgrade and some else > programms I get a lot of this error: > >> "Fatal error 'Cannot allocate red zone for initial thread' at line 382 > >> in file /usr/src/lib/libthr/thread/thr_init.c (errno = 12)", and coredump > then. > >> > >> googlin' give me feeling that it's good known sort of issue, but I > couldn't find any example of soving > >> > >> just where to look to solve it? > > > > Try manually rebuilding portupgrade and the ports that depend on it. > > > > My -current ports are old, but do something like this: > > > > # pkg_which /usr/local/sbin/portupgrade > > portupgrade-devel-2.3.0_5 > > > > # pkg_info -r portupgrade-devel-2.3.0_5 > > Information for portupgrade-devel-2.3.0_5: > > > > Depends on: > > Dependency: db41-4.1.25_4 > > Dependency: ruby-1.8.6,1 > > Dependency: perl-5.8.8 > > Dependency: ruby18-bdb-0.6.0 > > > > # pkg_info -oq db41-4.1.25_4 ruby-1.8.6,1 perl-5.8.8 ruby18-bdb-0.6.0 > > databases/db41 > > lang/perl5.8 > > lang/ruby18 > > databases/ruby-bdb > > > > So you'd rebuild those 4 ports and ports-mgmt/portupgrade. According > > to a recent post, you might only need to rebuild the ruby related ports > > and portupgrade. > > > > Disclaimer: I have not gone through this, just reiterating what I saw > > in a recent post. > > > > I'd already rebuilt portupgrade without recompiling dependencies - it's not > help. > ok, will try with dependencies. > but issue is not only in portupgrade as i wrote above, it sounds like more > global problem... > Some of your old programs end up linked to both old libc.so.6 and new libc.so.7 (through the shared library dependencies). Cheers, -- Ruslan Ermilov ru@FreeBSD.org FreeBSD committer