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: Mon, 3 Jun 2002 15:24:24 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: numerous bugs i've found in cygwin while developing XEmacs
Message-ID: <20020603192424.GA26504@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20020603132129 DOT H269776 AT lidp DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20020603132129.H269776@lidp.com>
User-Agent: Mutt/1.3.23.1i

On Mon, Jun 03, 2002 at 01:21:30PM -0500, Michael Potter wrote:
>> >[1] mmap[] and fork[].  The "pdump" [portable dumper] method of
>> > implementing undumping for XEmacs writes out all the data into
>> > a large file during building, and then reads it in when the
>> > program starts.  the file looks like this:
>> >-rw-r--r--    1 Ben Wing None      3280684 Jun  2 02:58 xemacs.dmp
>> >
>> >if mmap support exists, it's loaded using mmap[].  This fails
>> > miserably when a fork[] happens, as the child evidently doesn't
>> > get the mmap[]ed data visible in it and thus seg faults occur.
>>
>> This is obviously not supposed to be the way things work.  It
>> can't be as simple as "mmap doesn't work across forks".
>
>It could be as simple as the example I submitted last night.
>That submission includes a sample program.
>
>June 02, 2002 20:32
>cygwin 1.3.10 fork+sockets+shmat/mmap=recreate_mmaps_after_fork_failed
>
>The sample uses shmat, but if someone is willing to work on it,
>I would be happy to submit the example using mmap.

If you are using the sysv shared memory in cygwin then that is a
work in progress.

If you're using the cygipc libarry, then it is presumably a bug in
that library, not cygwin.

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/