From owner-freebsd-current@FreeBSD.ORG Mon Oct 15 14:28:27 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 32C8216A417 for ; Mon, 15 Oct 2007 14:28:27 +0000 (UTC) (envelope-from sklarkin@gmail.com) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.225]) by mx1.freebsd.org (Postfix) with ESMTP id EC65213C467 for ; Mon, 15 Oct 2007 14:28:26 +0000 (UTC) (envelope-from sklarkin@gmail.com) Received: by nz-out-0506.google.com with SMTP id l8so863828nzf for ; Mon, 15 Oct 2007 07:28:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; bh=9hJdV/7zIhh9rsGbyMUAEx0oDL1z4T/6w0je5BbHd1g=; b=dWud3gqsad9uHadBkKAgiIx8zJZ89XS77fXYYWXGmxq1lTdHjQ24DMcxXU+6AnGWdxwapzlFsxHYQjv+XzBb8Gd5sZDBFqrFjVqdAYYA8qRN3ix5W627b6Kp/Pl7g+GK5SD9b3RWNYPW5tvJB5cKnxEcFv3frEAYIcjANAH73uM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=cL3kJhAyhhPUDEU/5cCVFZncUSILFdIwFC71ozF64VD8wtOUTxA4HLqGjdnV0V73+Nkj52YDMgt8kaMw/BbJmu6BrS47oAfMqL+cIomDAH4cBmU7rsUf6h0MdSJ6qGARf7hlafT+0AVULei1FNC5jcwoRfvGvs0+prmaoIffFZ8= Received: by 10.141.42.10 with SMTP id u10mr2678540rvj.1192458503170; Mon, 15 Oct 2007 07:28:23 -0700 (PDT) Received: by 10.140.185.8 with HTTP; Mon, 15 Oct 2007 07:28:23 -0700 (PDT) Message-ID: <5b150c9c0710150728i27d2d812u5d0d1c2a8f6aad5f@mail.gmail.com> Date: Mon, 15 Oct 2007 18:28:23 +0400 From: sklarkin To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 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:28:27 -0000 Ruslan Ermilov wrote: > 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, thanks, Ruslan that's clear, i am going rebuild problem pakages with dependencies