From owner-freebsd-hackers  Fri Sep 19 01:35:36 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id BAA25214
          for hackers-outgoing; Fri, 19 Sep 1997 01:35:36 -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 BAA25192;
          Fri, 19 Sep 1997 01:35:30 -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 KAA12845;
	Fri, 19 Sep 1997 10:34:28 +0200 (CEST)
To: Mike Smith <mike@smith.net.au>
cc: Julian Elischer <julian@whistle.com>, Andrew Atrens <atrens@nortel.ca>,
        hackers@freebsd.org, gram@cdsec.com, freebsd-bugs@freebsd.org
Subject: Re: Bug in malloc/free 
In-reply-to: Your message of "Fri, 19 Sep 1997 16:22:04 +0930."
             <199709190652.QAA01100@word.smith.net.au> 
Date: Fri, 19 Sep 1997 10:34:28 +0200
Message-ID: <12843.874658068@critter.freebsd.dk>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In message <199709190652.QAA01100@word.smith.net.au>, Mike Smith writes:
>> 
>> probably a printf or other stdio function
>
>I *know* this. 8) I'm just trying to find the sucker.  The 'ddd' example 
>looked like it was spinning in abort(), which doesn't look like it will
>actually come back and call malloc() again.  In olden days, 
>if MALLOC_STATS was defined when malloc() was built, the stats dump 
>used fprintf(), but this is not the case with 3.x.

Some time ago abort() was changed to that it would call __flush(),
because some standard said so.  I still think this is unwise.

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