From owner-freebsd-current@FreeBSD.ORG Wed Mar 3 02:51:49 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 92C3416A4CE; Wed, 3 Mar 2004 02:51:49 -0800 (PST) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8661443D31; Wed, 3 Mar 2004 02:51:49 -0800 (PST) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id 82F715C7B0; Wed, 3 Mar 2004 02:51:49 -0800 (PST) Date: Wed, 3 Mar 2004 02:51:49 -0800 From: Alfred Perlstein To: David Xu Message-ID: <20040303105149.GH56622@elvis.mu.org> 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.2.1i cc: current@freebsd.org 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:51:49 -0000 * Alfred Perlstein [040303 02:46] 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. > > Is there a workaround? I sort of see what you are saying: ~ % ldd `which mplayer` /usr/local/bin/mplayer: libpng.so.5 => /usr/local/lib/libpng.so.5 (0x2828e000) libz.so.2 => /lib/libz.so.2 (0x282b0000) libfreetype.so.9 => /usr/local/lib/libfreetype.so.9 (0x282bd000) libncurses.so.5 => /lib/libncurses.so.5 (0x28320000) libGL.so.1 => /usr/X11R6/lib/libGL.so.1 (0x2835c000) libXv.so.1 => /usr/X11R6/lib/libXv.so.1 (0x283c9000) libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x283ce000) libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x283dd000) libpthread.so.1 => /usr/lib/libpthread.so.1 (0x284a5000) libiconv.so.3 => /usr/local/lib/libiconv.so.3 (0x284c8000) libintl.so.6 => /usr/local/lib/libintl.so.6 (0x285b7000) libm.so.2 => /lib/libm.so.2 (0x285bf000) libc.so.5 => /lib/libc.so.5 (0x285d7000) libc_r.so.5 => /usr/lib/libc_r.so.5 (0x286a2000) I see somehow it got linked against BOTH libpthread and libc_r, there has to be a way to prevent that sort of bogus linkage from happening. :( Or at least make it work right when it does happen... -- - Alfred Perlstein - Research Engineering Development Inc. - email: bright@mu.org cell: 408-480-4684