From owner-freebsd-bugs Thu Sep 18 23:54:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA19133 for bugs-outgoing; Thu, 18 Sep 1997 23:54:55 -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 XAA19115; Thu, 18 Sep 1997 23:54:42 -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 QAA01100; Fri, 19 Sep 1997 16:22:04 +0930 (CST) Message-Id: <199709190652.QAA01100@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Julian Elischer cc: Mike Smith , Andrew Atrens , hackers@FreeBSD.ORG, gram@cdsec.com, phk@critter.freebsd.dk, freebsd-bugs@FreeBSD.ORG Subject: Re: Bug in malloc/free In-reply-to: Your message of "Thu, 18 Sep 1997 23:33:34 MST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 19 Sep 1997 16:22:04 +0930 From: Mike Smith Sender: owner-freebsd-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > 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. mike