From owner-freebsd-current  Thu Oct 17 11:46:12 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id LAA20773
          for current-outgoing; Thu, 17 Oct 1996 11:46:12 -0700 (PDT)
Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA20766
          for <current@freebsd.org>; Thu, 17 Oct 1996 11:46:06 -0700 (PDT)
Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id MAA19565; Thu, 17 Oct 1996 12:45:44 -0600 (MDT)
Date: Thu, 17 Oct 1996 12:45:44 -0600 (MDT)
Message-Id: <199610171845.MAA19565@rocky.mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
To: Poul-Henning Kamp <phk@critter.tfs.com>
Cc: Nate Williams <nate@mt.sri.com>, current@freebsd.org
Subject: Re: Weirdness in current 
In-Reply-To: <4105.845577552@critter.tfs.com>
References: <199610171805.MAA19142@rocky.mt.sri.com>
	<4105.845577552@critter.tfs.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> >Stack corruption bugs are a *bugger* to find.
> 
> I don't know of any reliable & simple way to catch that kind of bug.

Port your software to SunOS/Slolaris and run Purify on it. :)

> I once made a gross hack on a Pyramid, such that checksum of the stack
> was made at every function call and record written to file at the
> return recording match/nomatch.

This is basically what Purify does..


Nate