From owner-freebsd-hackers  Thu Sep 18 22:23:58 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id WAA12389
          for hackers-outgoing; Thu, 18 Sep 1997 22:23:58 -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 WAA12358;
          Thu, 18 Sep 1997 22:23:48 -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 OAA00674;
	Fri, 19 Sep 1997 14:51:36 +0930 (CST)
Message-Id: <199709190521.OAA00674@word.smith.net.au>
X-Mailer: exmh version 2.0zeta 7/24/97
To: "Andrew Atrens" <atrens@nortel.ca>
cc: 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 "18 Sep 1997 23:41:00 EDT."
             <199709190401.VAA06335@hub.freebsd.org> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 19 Sep 1997 14:51:34 +0930
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> 
> ^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