From owner-freebsd-threads@FreeBSD.ORG Sat Jun 5 09:17:02 2004 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 14EFE16A4CE; Sat, 5 Jun 2004 09:17:02 -0700 (PDT) Received: from mail.mcneil.com (rrcs-west-24-199-45-54.biz.rr.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id E857743D31; Sat, 5 Jun 2004 09:17:01 -0700 (PDT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id D2388FD1D8; Sat, 5 Jun 2004 09:16:59 -0700 (PDT) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 06005-04; Sat, 5 Jun 2004 09:16:59 -0700 (PDT) Received: from [24.199.45.54] (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id EA45CFD1D7; Sat, 5 Jun 2004 09:16:58 -0700 (PDT) From: Sean McNeil To: Daniel Eischen In-Reply-To: References: Content-Type: text/plain Message-Id: <1086452218.6274.28.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Sat, 05 Jun 2004 09:16:58 -0700 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com cc: Tim Robbins cc: freebsd-amd64@freebsd.org cc: freebsd-threads@freebsd.org Subject: Re: All my amd64 problems appear to be KSE X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jun 2004 16:17:02 -0000 On Sat, 2004-06-05 at 09:06, Daniel Eischen wrote: > On Sun, 6 Jun 2004, Tim Robbins wrote: > > > On Sat, Jun 05, 2004 at 10:22:58AM -0400, Daniel Eischen wrote: > > > On Fri, 4 Jun 2004, Sean McNeil wrote: > > > > > > > On Fri, 2004-06-04 at 21:06, Daniel Eischen wrote: > > > > > On Fri, 4 Jun 2004, Sean McNeil wrote: > > > > > > > > > > > I just switched over to libc_r via. libmap.conf and I no longer get any > > > > > > mysterious crashes of applications in gnome. My gnome-terminals and > > > > > > everything else are just fine now. > > > > > > > > > > How were you using libpthread? It's best to use libmap.conf > > > > > to map everything to libpthread so that libc_r isn't pulled > > > > > in by libraries still linked to it. > > > > > > > > This is a completely rebuilt machine from a working i386 install that > > > > has tracked -current forever. There is absolutely nothing that is > > > > compiled and pointing to libc_r. > > > > > > Sorry, unless you have tried using libmap to map libc_r to > ^^^^^^^^^^^^^^^^^^^^^^^ > > > libpthread, I don't trust that. > ^^^^^^^^^^ > > ??? > > This is the first thing that I would ask anyone to try, and it's > very simple to do. Noone (or do we now spell it as 'no_one' ;-)) > has said, "yes, I've done that and it doesn't help". I am 100% certain that I can. I must be no_one :) See my other email. I'm positive that since not a single shared object is using libc_r nor any application - I actually ran the find on all files after the email instead of just "*.so*" - adding a map of libc_r to libthread.so.1 would be a noop for me. > > I can corroborate what Sean is saying. There is definitely something wrong > > with KSE on amd64 (I haven't tried it on i386.) I've been chasing it down, > > on-and-off, for about a month, but have come up with nothing so far. > > gnome-terminal and xmms are two examples of applications that have gone > > from unusable to usable after changing from libpthread to libc_r. Mozilla > > may also be affected, but I'm less sure of that. The applications in > > question just mysteriously vanish, sometimes with signal 10 or 11, sometimes > > with no signal in the kernel log at all. > > Is it something recent that broke? Last I knew, libpthread was working > on amd64 with mozilla & kde. That I cannot tell you. I bought my amd64 about a week ago and it hasn't worked with kse. I've only managed to get everything converted about 3 days ago, so I don't have much history. I would prefer not reverting to a release to test, but that is an option if no other means of tracking down the problem presents itself. Sean