This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
RE: numerous bugs i've found in cygwin while developing XEmacs
- From: Michael Potter <pottmi at lidp dot com>
- To: cygwin at cygwin dot com
- Date: Mon, 3 Jun 2002 15:59:45 -0500
- Subject: RE: numerous bugs i've found in cygwin while developing XEmacs
- Organization: Life Insurance Data Processing Incorporated
- Phone: +1 630 829 7015
- Reply-to: pottmi at lidp dot com
> > > >[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.
>
>
> You should resubmit as an mmap only bug. Cygipc's shmat support uses
> mmap, and cygwins 'native' shmat support is in development. Chances are,
> any shmat bug reports will (unfortunately) end up in /dev/null.
>
> Rob
Just did.
--
Michael Potter
pottmi@lidp.com
--
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/