From owner-freebsd-hackers  Thu Sep 18 23:47:48 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id XAA18529
          for hackers-outgoing; Thu, 18 Sep 1997 23:47:48 -0700 (PDT)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA18495;
          Thu, 18 Sep 1997 23:47:37 -0700 (PDT)
Received: (from daemon@localhost)
	by alpo.whistle.com (8.8.5/8.8.5) id XAA20189;
	Thu, 18 Sep 1997 23:34:20 -0700 (PDT)
Received: from current1.whistle.com(207.76.205.22)
 via SMTP by alpo.whistle.com, id smtpd020186; Fri Sep 19 06:34:18 1997
Date: Thu, 18 Sep 1997 23:33:34 -0700 (PDT)
From: Julian Elischer <julian@whistle.com>
To: Mike Smith <mike@smith.net.au>
cc: Andrew Atrens <atrens@nortel.ca>, hackers@FreeBSD.ORG, gram@cdsec.com,
        phk@critter.freebsd.dk, freebsd-bugs@FreeBSD.ORG
Subject: Re: Bug in malloc/free 
In-Reply-To: <199709190521.OAA00674@word.smith.net.au>
Message-ID: <Pine.BSF.3.95.970918233308.1895E-100000@current1.whistle.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


probably a printf or other stdio function

On Fri, 19 Sep 1997, Mike Smith wrote:

> > 
> > ^Cddd in malloc(): warning: recursive call.
> > Virtual memory exceeded in `new'
> > 
> > After reading Graham's thread I relinked it against libgnumalloc, and low
> > and behold it works like a charm !
> > 
> > Does this point to an incompatibility problem between phkmalloc and g++
> > compiled code ?
> 
> Something in malloc, somehow, is calling malloc() again, by the look of 
> it. 
> 
> Does libg++ define any replacements for any of the standard C library 
> functions?  I've been going through just about *everything* I can find
> in case Poul has missed something; there is nothing in any of the 
> malloc-called code (mostly just abort()) that is likely to be relevant 
> to this.
> 
> mike
> 
> 
>