From owner-freebsd-bugs  Thu Sep 18 22:41:30 1997
Return-Path: <owner-freebsd-bugs>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id WAA13732
          for bugs-outgoing; Thu, 18 Sep 1997 22:41:30 -0700 (PDT)
Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.26])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA13723;
          Thu, 18 Sep 1997 22:41:27 -0700 (PDT)
Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1])
	by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id HAA12159;
	Fri, 19 Sep 1997 07:40:56 +0200 (CEST)
To: "Andrew Atrens" <atrens@nortel.ca>
cc: hackers@freebsd.org, freebsd-bugs@freebsd.org
Subject: Re: Bug in malloc/free (was: Memory leak in getservbyXXX?) 
In-reply-to: Your message of "18 Sep 1997 17:59:00 EDT."
             <199709182204.AAA11611@critter.freebsd.dk> 
Date: Fri, 19 Sep 1997 07:40:55 +0200
Message-ID: <12157.874647655@critter.freebsd.dk>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-bugs@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In message <199709182204.AAA11611@critter.freebsd.dk>, "Andrew Atrens" writes:
>In message "Bug in malloc/free (was: Memory leak in getservbyXXX?)", phk@critt
>er.freebsd.dk writes:
>> 
>
>> This is about the only way you could get it to loop I think.  That means
>> that somebody wrote to memory malloc hadn't passed them (ie: your code).
>> 
>> 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.
>
>Why not have free() shred memory its releasing? Shredding memory with high
>values can often cause the offending code (which is still attempting
>to r/w this memory) to bus error.

options 'J' does that.

--
Poul-Henning Kamp             FreeBSD coreteam member
phk@FreeBSD.ORG               "Real hackers run -current on their laptop."