Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT cygwin DOT com>
List-Help: <mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT cygwin DOT com
Delivered-To: mailing list cygwin-developers AT cygwin DOT com
Date: Sun, 24 Mar 2002 16:23:08 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin-developers AT cygwin DOT com
Subject: Two fixup routines in fork_child seem misplaced (Corinna, Robert)
Message-ID: <20020324212308.GA9604@redhat.com>
Reply-To: cygwin-developers AT cygwin DOT com
Mail-Followup-To: cygwin-developers AT cygwin DOT com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.23.1i

There are two fixup routines in fork_child which seem to be too late in
fork process to be reliable: fixup_shms_after_fork and fixup_mmaps_after_fork.

Both occur after the last synchronization with the parent but may need to
rely on the parent's state, if I am reading things correctly.

I think this accounts for the strange behavior that was mentioned in the
cygwin mailing list with mmap.

There is obviously no shm usage these days.  I didn't look closely enough to see
if the regions that are being mapped are coming from the parent.  Maybe they're
just coming from the server, now that I think about it.  That would make more
sense.

cgf