From owner-freebsd-hackers Thu Sep 18 21:02:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA06369 for hackers-outgoing; Thu, 18 Sep 1997 21:02:41 -0700 (PDT) Received: from bcarsde4.localhost (mailgate.nortel.ca [192.58.194.74]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA06335; Thu, 18 Sep 1997 21:01:49 -0700 (PDT) Message-Id: <199709190401.VAA06335@hub.freebsd.org> Received: from bcars520.ott.bnr.ca (actually 47.128.5.188) by bcarsde4.localhost; Thu, 18 Sep 1997 23:42:25 -0400 Received: from bnr.ca by bcars520.bnr.ca id <11183-0@bcars520.bnr.ca>; Thu, 18 Sep 1997 23:41:16 -0400 Date: 18 Sep 1997 23:41 EDT To: hackers@FreeBSD.ORG Cc: gram@cdsec.com, phk@critter.freebsd.dk, freebsd-bugs@FreeBSD.ORG From: "Andrew Atrens" Subject: Re: Bug in malloc/free Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Folks, By coincidence I *may* have seen a bug similar to Graham's last night... I'm using 3.0 current ( circa. Aug 08 ). I built `ddd-2.1.1.tar.gz', found in /pub/FreeBSD/distfiles which is a largely C++ interface for gdb and others. Unfortunately, when I tried to run it, it gobbled memory until it choked. I tried a second time, this time killing it with CTRL-C and observed: ^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 ? Just a thought, Andrew.