Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Sat, 29 Mar 2003 11:13:36 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Mozilla 1.3 built on cygwin? Message-ID: <20030329161336.GA20487@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20030329001348.GA1533@redhat.com> <20030329130437.GH1207@cygbert.vinschen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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/