Date: Fri, 19 Sep 1997 09:30:59 +0200 (SAT) From: Graham Wheeler <gram@cdsec.com> To: peter@spinner.dialix.com.au (Peter Wemm) Cc: hackers@freebsd.org Subject: Re: Bug in malloc/free Message-ID: <199709190730.JAA01763@cdsec.com> In-Reply-To: <199709190459.MAA07378@spinner.dialix.com.au> from "Peter Wemm" at Sep 19, 97 12:59:33 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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 ? > > Hmm, this particular thing sounds like a signal recursion problem.. That's exactly what one of my bugs was. I was doing memory allocation from within a SIGCHLD handler which caused this problem. That was fixed (about Tuesday) and got rid of the `recursive call' problem, but hasn't got rid of the (apparent) malloc circular list problem. It is this latter problem that is proving tricky now, and which seems to have disappeared after linking with libmalloc_d. -- Dr Graham Wheeler E-mail: gram@cdsec.com Citadel Data Security Phone: +27(21)23-6065/6/7 Internet/Intranet Network Specialists Mobile: +27(83)-253-9864 Firewalls/Virtual Private Networks Fax: +27(21)24-3656 Data Security Products WWW: http://www.cdsec.com/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199709190730.JAA01763>