From owner-freebsd-threads@FreeBSD.ORG Sat Jun 5 09:02:22 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 20A1616A4CE; Sat, 5 Jun 2004 09:02:22 -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 EF2B143D3F; Sat, 5 Jun 2004 09:02:21 -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 4E256FD1D8; Sat, 5 Jun 2004 09:02:21 -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-02; Sat, 5 Jun 2004 09:02:20 -0700 (PDT) Received: from [24.199.45.54] (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 75BF6FD1D7; Sat, 5 Jun 2004 09:02:20 -0700 (PDT) From: Sean McNeil To: Daniel Eischen In-Reply-To: References: Content-Type: text/plain Message-Id: <1086451339.6274.18.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Sat, 05 Jun 2004 09:02:20 -0700 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com 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:02:22 -0000 On Sat, 2004-06-05 at 07:22, 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. I would have to say that is extremely myopic of you. Regardless of whether you trust me or not, it doesn't change what I have reported. kse is broken in some respect on amd64. For my own assurances, I have done the following: find / -name "*.so*" -exec ldd {} \; |& grep libc_r result was /usr/lib/libc_r.so.5: /usr/lib/libc_r.so: ldd: /usr/src/lib/compat/compat22/libc_r.so.3.0.bz2.uu: not a dynamic executableldd: /usr/src/lib/compat/compat3x.i386/libc_r.so.3.gz.uu: not a dynamic executable ldd: /usr/src/lib/compat/compat3x.i386/libc_r.so.4.gz.uu: not a dynamic executable ldd: /usr/src/lib/compat/compat4x.alpha/libc_r.so.4.bz2.uu: not a dynamic executable ldd: /usr/src/lib/compat/compat4x.i386/libc_r.so.4.bz2.uu: not a dynamic executable /usr/obj/usr/src/amd64/usr/lib/libc_r.so.5: /usr/obj/usr/src/amd64/usr/lib/libc_r.so: /usr/obj/usr/src/lib/libc_r/libc_r.so: /usr/obj/usr/src/lib/libc_r/libc_r.so.5: So as I stated earlier, there is absolutely nothing on my system that is compiled and pointing to libc_r. It is my opinion that it is always better to give a person the benefit of doubt regarding a claim. What I am looking for here is something constructive in a way of suggesting things I can do to assist in tracking down the problems I have seen. Can anyone give me ideas? I'm sort of stuck with this because 1) gdb doesn't work with attaching to a process that uses kse. This makes gnome's crash dialog and reporting mechanism non-functional. 2) I've tried --disable-crash-dialog when executing an application but that doesn't seem to have an effect. The crash dialog keeps getting in my way. I need some way to get these applications to dump core so I can take a look at a backtrace. Any help in accomplishing that would be highly appreciated. Hopefully it will help in resolving the issues with kse on amd64 as well. Cheers, Sean