Date: Wed, 21 Aug 2002 23:38:20 +0800 From: KT Sin <ktsin@acm.org> To: Martin Blapp <mb@imp.ch> Cc: Mark Santcroos <marks@ripe.net>, freebsd-current@FreeBSD.ORG Subject: Re: Solved: CURRENT and P-IV problems Message-ID: <20020821153820.GA12394@sarang.Singapore.Sun.COM> In-Reply-To: <20020821172613.L34509-100000@levais.imp.ch> References: <20020821152306.GE1348@laptop.6bone.nl> <20020821172613.L34509-100000@levais.imp.ch>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi I believe this is caused by the pre-released version of gcc in the system. I started seeing this problem one week after I upgraded my hardware to Pentium 4 in May. Two weeks ago, I built the final release version of gcc 3.1.1 in the ports and used that to compile the kernel and userlands. All the strange signals have disappeared since then. Good-luck, kt On Wed, Aug 21, 2002 at 05:27:24PM +0200, Martin Blapp wrote: > > Hi, > > > > The 2nd one fails at exactly the same point, that can't be coindedence. > > > Also with a signal 10. (libutil) > > > > > > The 3rd ended somewhere else(games/rogue), but now with signal 4. > > > > > > Doing the 4rd now. > > > > Which ends with signal 11 in usr.sbin/devinfo/ ... > > > > Mark > > May this be the memory corruption other users see (Alfred, David) ? > > I'll start again a new row of 10 builds here and see where it > ends. > > Martin > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020821153820.GA12394>