From owner-freebsd-current Fri Apr 14 6:40:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 58B0437B57F for ; Fri, 14 Apr 2000 06:40:34 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id OAA03696; Fri, 14 Apr 2000 14:50:08 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Peter Jeremy Cc: John Polstra , current@freebsd.org Subject: Re: MLEN and crashes In-reply-to: Your message of "Fri, 14 Apr 2000 09:35:43 +1000." <00Apr14.093744est.115286@border.alcanet.com.au> Date: Fri, 14 Apr 2000 14:50:08 +0200 Message-ID: <3694.955716608@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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