Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Sat, 29 Mar 2003 11:13:36 -0500
From:	Christopher Faylor <cgf-rcm AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Mozilla 1.3 built on cygwin?
Message-ID:	<20030329161336.GA20487@redhat.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<20030329001348 DOT GA1533 AT redhat DOT com> <LPEHIHGCJOAIPFLADJAHEEKLDHAA DOT chris AT atomice DOT net> <20030329130437 DOT GH1207 AT cygbert DOT vinschen DOT de>
Mime-Version:	1.0
In-Reply-To:	<20030329130437.GH1207@cygbert.vinschen.de>
User-Agent:	Mutt/1.5.1i

On Sat, Mar 29, 2003 at 02:04:37PM +0100, Corinna Vinschen wrote:
>On Win32, the original state of the memory is treated as genuin state for
>each process.  Therefore child processes don't inherit the changes from
>their parent processes but instead they begin with a fresh unchanged memory
>as it was before the first process wrote to it.

Right.  I played around with various uses of VirtualProtect to try to
work around this with no luck.  It was almost like Microsoft was purposely
twarting what seems like a reasonable use of memory mapping.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -