This is the mail archive of the
cygwin-developers@cygwin.com
mailing list for the Cygwin project.
Re: newlib/libc/stdlib/mallocr.c
- From: Earnie Boyd <earnie_boyd at yahoo dot com>
- To: Earnie Boyd <MinGW-Dvlpr at lists dot SF dot Net>
- Cc: Robert Collins <robert dot collins at itdomain dot com dot au>, Earnie Boyd <Cygwin-Developers at Cygwin dot Com>
- Date: Tue, 02 Apr 2002 08:15:06 -0500
- Subject: Re: newlib/libc/stdlib/mallocr.c
- References: <FC169E059D1A0442A04C40F86D9BA76008AC0B@itdomain003.itdomain.net.au> <3CA9ADBC.B86E80B0@yahoo.com>
- Reply-to: Earnie Boyd <Cygwin-Developers at Cygwin dot Com>
Earnie Boyd wrote:
>
> Robert Collins wrote:
> >
> > > -----Original Message-----
> > > From: Earnie Boyd [mailto:earnie_boyd@yahoo.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.
> >
>
> Does the "latest dlmalloc.c" == "newlib/libc/stdlib/mallocr.c"? Could
> your problems be solely related to "latest dlmalloc.c"? Could your
> problems also result from other defaults that
> "newlib/libc/stdlib/mallocr.c" overrides?
>
Oh, and _WIN32 would #define HAVE_MMAP 0 anyway. I just realized you
were discussing a non-cygwin program.
Earnie.
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com