From owner-freebsd-current Thu Aug 22 3:26:14 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C77CE37B400; Thu, 22 Aug 2002 03:26:10 -0700 (PDT) Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id 02CDE43E65; Thu, 22 Aug 2002 03:26:10 -0700 (PDT) (envelope-from marks@ripe.net) Received: from x54.ripe.net (x54.ripe.net [193.0.1.54]) by birch.ripe.net (8.12.5/8.11.6) with ESMTP id g7MAPsBG000769; Thu, 22 Aug 2002 12:25:54 +0200 Received: (from marks@localhost) by x54.ripe.net (8.11.6/8.11.6) id g7MAPsL17461; Thu, 22 Aug 2002 12:25:54 +0200 Date: Thu, 22 Aug 2002 12:25:53 +0200 From: Mark Santcroos To: Terry Lambert Cc: Soeren Schmidt , Martin Blapp , Don Lewis , ktsin@acm.org, freebsd-current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Memory corruption in CURRENT Message-ID: <20020822102553.GA17453@ripe.net> References: <200208220909.g7M99NcS077303@freebsd.dk> <3D64B005.6657A3B5@mindspring.com> <20020822100014.GA17143@ripe.net> <3D64BA1F.B3C8C8E0@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3D64BA1F.B3C8C8E0@mindspring.com> User-Agent: Mutt/1.3.25i X-Handles: MS6-6BONE, MS32260-NIC, MS18417-RIPE X-RIPE-Spam-Status: NONE ; -1034 X-RIPE-Spam-Level: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Aug 22, 2002 at 03:17:03AM -0700, Terry Lambert wrote: > Mark Santcroos wrote: > > On Thu, Aug 22, 2002 at 02:33:57AM -0700, Terry Lambert wrote: > > > options DISABLE_PSE > > > options DISABLE_PG_G > > > > Coming up next in this theater :-) > > > > btw, how does the report that using the other compiler fixed everything > > for KT fit in? It looks indeed like it is a 'winner'. The buildworld is still running but getting further already than the previous 10. > Coincidentally. It's hard to trigger the bug, so it's easy to > work around it accidently. Thats very true indeed. I can take that as a good 'explanation'. I remember you talking about this PSE problems earlier and more often. Is it fixable? I assume we would like to turn these options back on as they improve performance don't they? 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