Date: Wed, 3 Mar 2004 11:57:10 +0100 From: Robert Blacquiere <freebsd-current@guldan.demon.nl> To: current@freebsd.org Subject: Re: fix for libpthread Message-ID: <20040303105710.GB51613@bombur.guldan.demon.nl> In-Reply-To: <20040303104657.GG56622@elvis.mu.org> References: <20040303061144.GE56622@elvis.mu.org> <404592F5.1060206@freebsd.org> <20040303104657.GG56622@elvis.mu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Mar 03, 2004 at 02:46:57AM -0800, Alfred Perlstein wrote: > * David Xu <davidxu@freebsd.org> [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!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040303105710.GB51613>