Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Date: Sat, 1 Jul 2000 22:45:20 -0400
Message-Id: <200007020245.WAA14181@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: asharji AT plg2 DOT math DOT uwaterloo DOT ca
CC: cygwin AT sourceware DOT cygnus DOT com
In-reply-to: <Pine.SOL.3.96.1000630214754.5827A-100000@plg2.math.uwaterloo.ca>
	(asharji AT plg2 DOT math DOT uwaterloo DOT ca)
Subject: Re: user defined malloc
References:  <Pine DOT SOL DOT 3 DOT 96 DOT 1000630214754 DOT 5827A-100000 AT plg2 DOT math DOT uwaterloo DOT ca>


> My question is do I have to also override the _malloc_r routine, and
> if so, could someone provide some information or a link on what is
> required?  It appears to be a reentrant version of malloc.

Yup, newlib is heavy into reentrancy.  However, _malloc_r isn't
exported by cygwin1.dll and cygwin doesn't expect your program to
replace it.  I'm not sure how much of a "bug" this is, but I'm open
for suggestions.  Might want to ask on the newlib list also, I'm sure
they have really good reasons to call the reentrant malloc.

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com