Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 05 Jun 2004 09:16:58 -0700
From:      Sean McNeil <sean@mcneil.com>
To:        Daniel Eischen <eischen@vigrid.com>
Cc:        freebsd-threads@freebsd.org
Subject:   Re: All my amd64 problems appear to be KSE
Message-ID:  <1086452218.6274.28.camel@server.mcneil.com>
In-Reply-To: <Pine.GSO.4.10.10406051157001.7353-100000@pcnet5.pcnet.com>
References:  <Pine.GSO.4.10.10406051157001.7353-100000@pcnet5.pcnet.com>

next in thread | previous in thread | raw e-mail | index | archive | help
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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1086452218.6274.28.camel>