From owner-freebsd-current@FreeBSD.ORG Thu Aug 3 12:09:39 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0B73A16A4E2 for ; Thu, 3 Aug 2006 12:09:39 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA9B843D4C for ; Thu, 3 Aug 2006 12:09:33 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.ntplx.net (8.13.7/8.13.7/NETPLEX) with ESMTP id k73C9VHa005806; Thu, 3 Aug 2006 08:09:32 -0400 (EDT) Date: Thu, 3 Aug 2006 08:09:31 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Kip Macy In-Reply-To: <20060802151129.R79030@demos.bsdclusters.com> Message-ID: References: <1154527524.93666.22.camel@tobias.home.web-wahnsinn.de> <20060802194817.GA53062@what-creek.com> <20060802135246.J66851@demos.bsdclusters.com> <20060802141115.D71770@demos.bsdclusters.com> <20060802151129.R79030@demos.bsdclusters.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) Cc: freebsd-current@freebsd.org, John Birrell , Tobias Gro?er Subject: Re: DTRACE build failure (/usr/obj/usr/src/tmp/usr/bin/ld: cannot find -lpthread) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Aug 2006 12:09:39 -0000 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