From owner-freebsd-current Thu Oct 17 12:22:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA23266 for current-outgoing; Thu, 17 Oct 1996 12:22:36 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.177]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA23247; Thu, 17 Oct 1996 12:22:15 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id VAA04245; Thu, 17 Oct 1996 21:21:11 +0200 (MET DST) To: Nate Williams cc: current@FreeBSD.org Subject: Re: Weirdness in current In-reply-to: Your message of "Thu, 17 Oct 1996 12:45:44 MDT." <199610171845.MAA19565@rocky.mt.sri.com> Date: Thu, 17 Oct 1996 21:21:11 +0200 Message-ID: <4243.845580071@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In message <199610171845.MAA19565@rocky.mt.sri.com>, Nate Williams writes: >> >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.. I said "simple" what Purify does can hardly be called "simple" :-) -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so.