From owner-freebsd-hackers Tue Sep 23 15:19:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA08893 for hackers-outgoing; Tue, 23 Sep 1997 15:19:17 -0700 (PDT) Received: from hokkshideh.jetcafe.org (hokkshideh.jetcafe.org [207.155.21.4]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA08872; Tue, 23 Sep 1997 15:19:12 -0700 (PDT) Received: from hokkshideh.jetcafe.org (localhost [127.0.0.1]) by hokkshideh.jetcafe.org (8.8.5/8.8.5) with ESMTP id PAA18505; Tue, 23 Sep 1997 15:18:16 -0700 (PDT) Message-Id: <199709232218.PAA18505@hokkshideh.jetcafe.org> X-Mailer: exmh version 2.0delta 6/3/97 To: "Jordan K. Hubbard" Cc: Poul-Henning Kamp , Graham Wheeler , hackers@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG Subject: Re: Bug in malloc/free (was: Memory leak in getservbyXXX?) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 23 Sep 1997 15:18:16 -0700 From: Dave Hayes Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jordan K Hubbard writes: >> This would indicate a bug of the class where memory is written to >> after being free()'ed, a kind of bug which phkmalloc makes no >> attempt to catch. > Man, I sure wish there was a copy of purify available for FreeBSD. > It's great at catching stuff like this! :( So was "leak", which was a DBM style wrapper to malloc/free. It would keep track of what you'd free'd and malloc'd and warn you when you were screwing up. Leak was public domain, but I have no idea where to get it. I have a hacked copy if anyone wants want. ------ Dave Hayes - Altadena CA, USA - dave@jetcafe.org >>> The opinions expressed above are entirely my own <<< Freedom Knight of Usenet - http://www.jetcafe.org/~dave/usenet Enjoyment is not a goal, it is a feeling that accompanies important ongoing activity