Date: Thu, 22 Aug 2002 14:27:11 +0200 From: Mark Santcroos <marks@ripe.net> To: Terry Lambert <tlambert2@mindspring.com> Cc: ktsin@acm.org, freebsd-current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Memory corruption in CURRENT Message-ID: <20020822122711.GF23616@laptop.6bone.nl> In-Reply-To: <3D64D762.56B10540@mindspring.com> References: <3D64CB76.80A0FA46@mindspring.com> <200208221141.g7MBfDRj007168@freebsd.dk> <20020822114359.GC23616@laptop.6bone.nl> <3D64D762.56B10540@mindspring.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Aug 22, 2002 at 05:21:54AM -0700, Terry Lambert wrote: > Mark Santcroos wrote: > > On Thu, Aug 22, 2002 at 01:41:13PM +0200, Soeren Schmidt wrote: > > > Sure, but I dont have the problem :) I can buildworld for days on my > > > (heavily overclocked btw) Athlon with no problems at all... > > > > Can you revert back to the system compiler and also compile your kernel > > with this options and do some buildworlds again? > > You are making the same mistake I did. No, you are making the same mistake as Soren ;-) I did ask KT, look at the 'To:' field. Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM 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?20020822122711.GF23616>