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: Tue, 28 Nov 2000 23:36:30 -0500
From: Chris Faylor <cgf AT redhat DOT com>
To: Zack Weinberg <zackw AT Stanford DOT EDU>
Cc: "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Subject: Re: [PATCH] Problems with Cygwin mmap/munmap (mmap.cc)
Message-ID: <20001128233630.A12353@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: Zack Weinberg <zackw AT Stanford DOT EDU>,
	"cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
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>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.11i
In-Reply-To: <20001128202753.I472@wolery.stanford.edu>; from zackw@Stanford.EDU on Tue, Nov 28, 2000 at 08:27:53PM -0800

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.

>On Tue, Nov 28, 2000 at 10:52:59PM -0500, Christopher Faylor wrote:
>>
>> 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?

cgf

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