From owner-freebsd-current@FreeBSD.ORG Wed Mar 3 02:57:28 2004 Return-Path: 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 7EAF316A4CE for ; Wed, 3 Mar 2004 02:57:28 -0800 (PST) Received: from guldan.demon.nl (cust.13.38.adsl.cistron.nl [62.216.13.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id E211A43D31 for ; Wed, 3 Mar 2004 02:57:27 -0800 (PST) (envelope-from robert@guldan.demon.nl) Received: from bombur.guldan.demon.nl ([192.168.201.3] helo=localhost) by guldan.demon.nl with esmtp (Exim 4.24; FreeBSD) id 1AyU3r-0004Fn-4Z; Wed, 03 Mar 2004 11:57:11 +0100 Date: Wed, 3 Mar 2004 11:57:10 +0100 From: Robert Blacquiere To: current@freebsd.org Message-ID: <20040303105710.GB51613@bombur.guldan.demon.nl> References: <20040303061144.GE56622@elvis.mu.org> <404592F5.1060206@freebsd.org> <20040303104657.GG56622@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040303104657.GG56622@elvis.mu.org> User-Agent: Mutt/1.4.1i X-Disclaimer: running FreeBSD X-Spam-Score: 0.0 (/) Subject: Re: fix for libpthread X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Wed, 03 Mar 2004 10:57:28 -0000 On Wed, Mar 03, 2004 at 02:46:57AM -0800, Alfred Perlstein wrote: > * David Xu [040303 00:09] wrote: > > Alfred Perlstein wrote: > > > > >This assertion doesn't seem necessary. Apply to > > >src/lib/libpthread/thread/thr_spinlock.c > > > > > As I saw some reports in the -CURRENT list, the panic is always > > triggered by mix up > > of libc_r and libpthread in same program. So to avoid other mysterious > > crashes, > > I'd like keep the code there, it is now used to check the problem. > > Can you clarify? Without this patch mplayer refuses to work for > me and crashes at startup. With the patch it runs just fine. I think what David wants is to locate misbehaved programs like mplayer. And then try to find a way to fix these programs instead of patching a good system, or we'll end up with a system like a known large producer of PC software and PC OS. I refuse to call it's name... > > Is there a workaround? I'd think something like pkg_delete -x mplayer? Maybe there is already a patch available for mplayer? Robert -- Microsoft: Where do you want to go today? Linux: Where do you want to go tomorrow? FreeBSD: Are you guys coming or what? OpenBSD: Hey guys you left some holes out there!