Date: 12 Dec 2002 15:37:43 -0500 From: Joe Marcus Clarke <marcus@marcuscom.com> To: James Pole <james.pole@paradise.net.nz> Cc: "Jacques A. Vidrine" <nectar@FreeBSD.ORG>, FreeBSD GNOME Users <gnome@FreeBSD.ORG> Subject: Re: Repeatable crash from nautilus2 Message-ID: <1039725463.2413.64.camel@gyros> In-Reply-To: <1039724894.235.9.camel@localhost> References: <20021211135451.G83245-100000@fubar.adept.org> <1039662104.233.7.camel@localhost> <20021212145509.GA13791@madman.nectar.cc> <1039710116.2413.8.camel@gyros> <20021212172708.GA28530@madman.nectar.cc> <1039724894.235.9.camel@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 2002-12-12 at 15:28, James Pole wrote: > On Fri, 2002-12-13 at 06:27, Jacques A. Vidrine wrote: > > On Thu, Dec 12, 2002 at 11:21:56AM -0500, Joe Marcus Clarke wrote: > > > For me, I use no CPUTYPE. I accept the OS's default optimizations, and > > > Nautilus 2 works fine for me on -STABLE and -CURRENT. Of course, with > > > -CURRENT, I had to rebuild all my ports recently after the compiler > > > upgrades. > > > > But it does not work on my dual Athlon, with CPUTYPE=k7, nor without > > CPUTYPE setting. Everything built today. > > Have you rebuilt everything, including the world? > > Just a wild guess, could it be a problem specific to AMD's Athlon > processors? I havn't, so far, seen anyone with Intel processors report > this bug -- or maybe I'm just imagining it. You're not imagining it. There could be a threading issue with Athalons. All my machines are Intel, and so far, only AMD users have reported these problems. Joe > > - James > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-gnome" in the body of the message -- PGP Key : http://www.marcuscom.com/pgp.asc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-gnome" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1039725463.2413.64.camel>