Date:	Sat, 19 Apr 2003 11:53:39 +0200
From:	"Eli Zaretskii" <eliz AT elta DOT co DOT il>
Sender:	halo1 AT zahav DOT net DOT il
To:	djgpp-workers AT delorie DOT com
Message-Id:	<9743-Sat19Apr2003115338+0300-eliz@elta.co.il>
X-Mailer:	emacs 21.3.50 (via feedmail 8 I) and Blat ver 1.8.9
In-reply-to:	<3E7B8D9D.EEE854B1@yahoo.com> (message from CBFalconer on Fri, 21
	Mar 2003 17:09:33 -0500)
Subject:	Re: nmalloc revisited
References:	<200303141601 DOT RAA26911 AT lws256 DOT lu DOT erisoft DOT se> <3E7B8D9D DOT EEE854B1 AT yahoo DOT com>
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> Date: Fri, 21 Mar 2003 17:09:33 -0500
> From: CBFalconer <cbfalconer AT yahoo DOT com>
> 
> The revised package is at:
> 
>    <http://cbfalconer.home.att.net/download/nmalloc.zip>

Sorry for such a long delay.

I've finally looked at your implementation of malloc-debug facilities,
and I have only one comment: I don't like the idea of redefining
`malloc' to `_malloc', `free' to `_free', etc.  Unless I'm missing
something, this precludes linking an application with the debuggery
code without recompiling all the app's code from scratch.  It means,
for example, that if I have a library for which I have no sources, and
that library calls `malloc' et al, I'm toast if I want malloc-debug.

What's the problem to use the hooks as they are used in malldbg.c
that's in the current DJGPP CVS?

- Raw text -