Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Date:	Wed, 29 Nov 2000 01:30:34 -0800
From:	"Zack Weinberg" <zackw AT Stanford DOT EDU>
To:	"cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Subject:	Re: [PATCH] Problems with Cygwin mmap/munmap (mmap.cc)
Message-ID:	<20001129013034.M472@wolery.stanford.edu>
References:	<200011281912 DOT eASJCmf13405 AT plmlir5 DOT mail DOT eds DOT com> <20001128114558 DOT R2285 AT wolery DOT stanford DOT edu> <20001128225259 DOT B11647 AT redhat DOT com> <20001128202753 DOT I472 AT wolery DOT stanford DOT edu> <20001128233630 DOT A12353 AT redhat DOT com>
Mime-Version:	1.0
User-Agent:	Mutt/1.2.5i
In-Reply-To:	<20001128233630.A12353@redhat.com>; from cgf@redhat.com on Tue, Nov 28, 2000 at 11:36:30PM -0500

On Tue, Nov 28, 2000 at 11:36:30PM -0500, Chris Faylor wrote:
> On Tue, Nov 28, 2000 at 08:27:53PM -0800, Zack Weinberg wrote:
> >[cgf - I'm cc:ing you despite the Reply-To: because when I last tried
> >to send mail to the cygwin list it bounced with a "You're not a
> >subscriber" message.]
> 
> ???  Hopefully you were sending email to cygwin-developers not cygwin.
> cygwin-developers is subscribe only but I'll add you to the "allow to
> post list", in case you do want to send something there.  This
> discussion is actually more appropriate for that list.

Yeah, it was probably that.  I wasn't paying really close attention.



> >> The problem, I think, is that VirtualAlloc space is not inherited.  We
> >> could kludge around this, like we do with fork, by copying the regions
> >> but that could slow down things a lot.
> >
> >Hm, is there any way cc1 can tell cygwin that it promises never to use
> >fork?
> 
> Not currently, no.
> 
> Maybe we need to implement a valloc that is not wasteful of memory?

If you implement it, we'll use it.  :)

zw

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

- Raw text -