error with thread

[Ruslan Ermilov]

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 at FreeBSD.org
FreeBSD committer