Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com content-class: urn:content-classes:message Subject: RE: newlib/libc/stdlib/mallocr.c MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 2 Apr 2002 23:01:42 +1000 X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Robert Collins" To: "Earnie Boyd" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g32D2Ue03528 > -----Original Message----- > From: Earnie Boyd [mailto:earnie_boyd AT yahoo DOT com] > Sent: Tuesday, April 02, 2002 10:57 PM > To: Robert Collins > Cc: Earnie Boyd > Subject: Re: newlib/libc/stdlib/mallocr.c > > > Robert Collins wrote: > > > > FWIW, I've had trouble with HAVE_MMAP on in dlmalloc :[. > Some systems > > seem to allocate memory differently than the HAVE_MMAP code > on win32 > > expected. > > > > "Some systems"! What do you mean? Well my XP Professional machine anyway. When I was tracking down the setup memory problem, I build a custom malloc - using the latest dlmalloc.c and encountered this. Rob