From owner-freebsd-current@FreeBSD.ORG Mon Feb 9 10:23:44 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 9304C16A4CE for ; Mon, 9 Feb 2004 10:23:44 -0800 (PST) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 793D443D3F for ; Mon, 9 Feb 2004 10:23:44 -0800 (PST) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 09BBF72DBF; Mon, 9 Feb 2004 10:23:44 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 0794A72DB5; Mon, 9 Feb 2004 10:23:44 -0800 (PST) Date: Mon, 9 Feb 2004 10:23:44 -0800 (PST) From: Doug White To: Jesse Guardiani In-Reply-To: <200402071438.21289.jesse@wingnet.net> Message-ID: <20040209101948.Q47197@carver.gumbysoft.com> References: <20040206185032.L20313@carver.gumbysoft.com> <200402071438.21289.jesse@wingnet.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: kdesu crash under 5.2-RELEASE with libkse via libmap.conf 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: Mon, 09 Feb 2004 18:23:44 -0000 On Sat, 7 Feb 2004, Jesse Guardiani wrote: > On Friday 06 February 2004 21:52, Doug White wrote: > > On Wed, 4 Feb 2004, Jesse Guardiani wrote: > > > If I run this: > > > > > > /usr/local/bin/kdesu --nonewdcop '/usr/local/bin/kcmshell clock --lang > > > en_US' > > > > > > And my libmap.conf looks like this: > > > > > > # /etc/libmap.conf > > > # > > > # candidate mapping > > > # > > > libc_r.so.5 libkse.so.1 # Everything uses 'libkse' by > > > default libc_r.so libkse.so > > > > > > > > > Then I get this: > > > > > > (no debugging symbols found)...(no debugging symbols found)... > > > > This isn't a crash, > > And what makes you think that? The KDE crash window popped up and I > clicked on the backtrace button. Well it forgot to mention why it halted. Usually it says something like: Program received signal SIGSEGV, Segmentation fault. Or the backtrace will be in abort(). I'll still try to reproduce this. In the interim, can you run ldd on the offending application and make sure it isn't linking against both libc_r and libpthread? If so, then you need to rebuild X and everything upwards. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org