From owner-freebsd-bugs Fri Sep 19 01:45:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA25901 for bugs-outgoing; Fri, 19 Sep 1997 01:45:44 -0700 (PDT) Received: from word.smith.net.au (word.smith.net.au [202.0.75.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA25891; Fri, 19 Sep 1997 01:45:38 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id SAA02922; Fri, 19 Sep 1997 18:10:31 +0930 (CST) Message-Id: <199709190840.SAA02922@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Poul-Henning Kamp cc: Mike Smith , Julian Elischer , Andrew Atrens , 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 10:34:28 +0200." <12843.874658068@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 19 Sep 1997 18:10:29 +0930 From: Mike Smith Sender: owner-freebsd-bugs@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. This is only an issue if the user supplies a custom _write handler for a FILE. The standard handler doesn't appear to have any opportunity for dynamic allocation. mike