Date: Mon, 9 Feb 2004 10:23:44 -0800 (PST) From: Doug White <dwhite@gumbysoft.com> To: Jesse Guardiani <jesse@wingnet.net> Cc: freebsd-current@freebsd.org Subject: Re: kdesu crash under 5.2-RELEASE with libkse via libmap.conf Message-ID: <20040209101948.Q47197@carver.gumbysoft.com> In-Reply-To: <200402071438.21289.jesse@wingnet.net> References: <bvs595$p9e$1@sea.gmane.org> <20040206185032.L20313@carver.gumbysoft.com> <200402071438.21289.jesse@wingnet.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040209101948.Q47197>