Date: Fri, 19 Sep 1997 10:34:28 +0200 From: Poul-Henning Kamp <phk@critter.freebsd.dk> 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 Message-ID: <12843.874658068@critter.freebsd.dk> In-Reply-To: Your message of "Fri, 19 Sep 1997 16:22:04 %2B0930." <199709190652.QAA01100@word.smith.net.au>
next in thread | previous in thread | raw e-mail | index | archive | help
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."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?12843.874658068>