This is the mail archive of the
cygwin-developers@cygwin.com
mailing list for the Cygwin project.
RE: newlib/libc/stdlib/mallocr.c
- From: "Robert Collins" <robert dot collins at itdomain dot com dot au>
- To: "Earnie Boyd" <Cygwin-Developers at Cygwin dot Com>
- Date: Tue, 2 Apr 2002 22:52:59 +1000
- Subject: RE: newlib/libc/stdlib/mallocr.c
> -----Original Message-----
> From: Earnie Boyd [mailto:earnie_boyd@yahoo.com]
> Sent: Tuesday, April 02, 2002 10:44 PM
> To: Earnie Boyd
> Subject: newlib/libc/stdlib/mallocr.c
>
>
> In my modifying Cygwin source for MSYS I began having issues
> with malloc and the offending pieces being within this
> source. I noticed that the HAVE_MMAP macro was set to 0 by
> default instead of 1 by default as Dave's documentation says
> that it does. Modifying the macro value to 1 caused all of
> the problems I was experiencing to disappear.
>
> Do other Cygwin developers see benefit for a patch to newlib?
>
> Should I create a newlib patch regardless of the benefit to Cygwin?
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.
Rob