Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 3 Aug 2006 08:09:31 -0400 (EDT)
From:      Daniel Eischen <deischen@freebsd.org>
To:        Kip Macy <kmacy@fsmware.com>
Cc:        freebsd-current@freebsd.org, John Birrell <jb@what-creek.com>, Tobias Gro?er <bsdlists@gmx.de>
Subject:   Re: DTRACE build failure (/usr/obj/usr/src/tmp/usr/bin/ld: cannot find -lpthread)
Message-ID:  <Pine.GSO.4.64.0608030804590.12639@sea.ntplx.net>
In-Reply-To: <20060802151129.R79030@demos.bsdclusters.com>
References:  <1154527524.93666.22.camel@tobias.home.web-wahnsinn.de> <20060802194817.GA53062@what-creek.com> <Pine.GSO.4.64.0608021611310.8714@sea.ntplx.net> <20060802135246.J66851@demos.bsdclusters.com> <Pine.GSO.4.64.0608021706040.8714@sea.ntplx.net> <20060802141115.D71770@demos.bsdclusters.com> <Pine.GSO.4.64.0608021800440.8714@sea.ntplx.net> <20060802151129.R79030@demos.bsdclusters.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 2 Aug 2006, Kip Macy wrote:

>> That sounds more like a bug with gdb/libthread_db.  It also doesn't
>> sound like a major bug either, like "signals are broken with KSE"
>> makes it sound.
>
> Uhhhmmm no it doesn't. And even if it did, it wouldn't explain why
> threaded processes become unkillable. In any event removing KSE makes
> the problem go away.

I've seen unthreaded processes become unkillable too.
And again, you can't comment on problems with threading
under sparc64 because KSE doesn't work there until
"someone steps up" and makes it work.  I've been using
libpthread under x86 without seeing any of the problems
you are describing.  I'm not discounting your problems,
but your advocating removal of KSE when it's been
very functional for a long time is very unjust.

-- 
DE



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.64.0608030804590.12639>