Date: Tue, 25 Sep 2001 16:57:01 -0700 (PDT) From: Julian Elischer <julian@elischer.org> To: Matt Dillon <dillon@earth.backplane.com> Cc: Peter Jeremy <peter.jeremy@alcatel.com.au>, hackers@FreeBSD.ORG Subject: Re: VM Corruption - stumped, anyone have any ideas? Message-ID: <Pine.BSF.4.21.0109251655020.56701-100000@InterJet.elischer.org> In-Reply-To: <200109252245.f8PMjpd05302@earth.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0109251655020.56701-100000>