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: Tue, 4 Jun 2002 15:08:12 -0500
From: Michael Potter <pottmi AT lidp DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: cygwin 1.3.10 mmap+fork+sockets=fixup_mmaps_after_fork
Message-ID: <20020604150811.W660772@lidp.com>
Reply-To: pottmi AT lidp DOT com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.19i
Organization: Life Insurance Data Processing Incorporated
Phone: +1 630 829 7015

> On Mon, Jun 03, 2002 at 03:57:07PM -0500, Michael Potter wrote:
> >
> > Enclosed is a sample program that demonstrates a bug with
> > mmap, fork, and sockets.  This sample is very similar to
> > on submitted by me on june 2, but this one eliminiates sysV ipc.
> >
> > here is the sample run:
> 
> Your example code works fine with Cygwin from current cvs HEAD.
> So I assume the problem has been fixed.
> Corinna
> 

Corinna,

We just tried the latest snap shot and the example fails.

I want to confirm that you ran the sample properly.

Did you do a "telnet hostname 5210" to allow the program to
continue the the second fork, which fails?

You will get the command prompt back because the sample
"daemonizes", but you need to telnet to it to allow
the daemon to continue.

-- 
Michael Potter

--
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/