From owner-freebsd-hackers Tue Sep 25 16: 9:24 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id 5EBCE37B407 for ; Tue, 25 Sep 2001 16:09:21 -0700 (PDT) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id QAA57214; Tue, 25 Sep 2001 16:57:02 -0700 (PDT) Date: Tue, 25 Sep 2001 16:57:01 -0700 (PDT) From: Julian Elischer To: Matt Dillon Cc: Peter Jeremy , hackers@FreeBSD.ORG Subject: Re: VM Corruption - stumped, anyone have any ideas? In-Reply-To: <200109252245.f8PMjpd05302@earth.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG The only way to get people to change their code is to make it complain at them when they compile it. If a stack is big, then that's "someone-else's" problem... I was thinking to only turn it on every now and then,.. On Tue, 25 Sep 2001, Matt Dillon wrote: > I really don't think it is necessary to hack up GCC to figure > out stack utilization. We have issues with only a few drivers > and it is fairly trivial (as my patch shows) to throw a pattern > into the kernel stack to determine how much is actually used. > > -Matt > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message