Date: Fri, 14 Apr 2000 14:50:08 +0200 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: Peter Jeremy <peter.jeremy@alcatel.com.au> Cc: John Polstra <jdp@polstra.com>, current@freebsd.org Subject: Re: MLEN and crashes Message-ID: <3694.955716608@critter.freebsd.dk> In-Reply-To: Your message of "Fri, 14 Apr 2000 09:35:43 %2B1000." <00Apr14.093744est.115286@border.alcanet.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <00Apr14.093744est.115286@border.alcanet.com.au>, Peter Jeremy write s: >Many years ago, I wrote a tool that analysed stack requirements by >parsing the assembler output from the compiler. It determined the >stack frame requirements and built a call flow graph to determine >total stack depth. It had some hooks to allow indirect function >calls to be specified manually. It couldn't handle alloca() (and >equivalents), but they were forbidden by the design standards. > > >What are other people's opinions on the usefulness of something >like this? Commit it either as a general tool or as a kernel targeted tool under src/tools. And the faster the better :-) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. 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?3694.955716608>