X-Recipient: archive-cygwin@delorie.com
X-SWARE-Spam-Status: No, hits=-0.6 required=5.0 	tests=AWL,BAYES_00,J_CHICKENPOX_34,SARE_MSGID_LONG40,SPF_PASS
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <20090331150728.GE12738@calimero.vinschen.de>
References: <bc2e28c70903310234p1fa23e9esfe4e4ca8f293fbef@mail.gmail.com> 	 <20090331112111.GB12738@calimero.vinschen.de> 	 <bc2e28c70903310441h7f354e5br99ecf91825231227@mail.gmail.com> 	 <20090331120843.GD12738@calimero.vinschen.de> 	 <20090331150728.GE12738@calimero.vinschen.de>
Date: Wed, 1 Apr 2009 11:19:28 +0530
Message-ID: <bc2e28c70903312249t63444b70la92732bb3a05afe5@mail.gmail.com>
Subject: Re: IPC,FORK on Windows 2008 Server
From: Yarlagadda Suresh <ysuresh.forum@gmail.com>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-IsSubscribed: yes
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

Thanks a ton for your quick response.

Could please let me know the patch version number, which includes the fix?

Cheers,
Suresh Kumar.

On Tue, Mar 31, 2009 at 8:37 PM, Corinna Vinschen
<corinna-cygwin@cygwin.com> wrote:
> On Mar 31 14:08, Corinna Vinschen wrote:
>> On Mar 31 17:11, Yarlagadda Suresh wrote:
>> > Hi,
>> >
>> > I am using shmget()/shmat() methods for getting the shared memory.
>> >
>> > I had tried running the same program which is given in the previous
>> > mention thread, the results are same as mentioned over there.
>>
>> I just tried that testcase with Cygwin 1.7 and it appears to work most
>> of the time. =A0 Unfortunately I can still reproduce the problem once per
>> about 30 forks.
>>
>> I'll look into fixing this for Cygwin 1.7. =A0However, please note that
>> there is no *really* foolproof method to fix this due to the way fork
>> has to be implemented using Win32 calls. =A0I can only make it much more
>> unlikely than today.
>
> I applied a patch to Cygwin which allocates the shmat() shared memory
> regions top-down, same as the mmap() regions. =A0This should make the
> observed effect at fork() pretty unlikely. =A0The patch will be in the
> next Cygwin 1.7.0 test release (in a couple of days).
>
>
> Thanks for the report,
> Corinna
>
> --
> Corinna Vinschen =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Please, send mails re=
garding Cygwin to
> Cygwin Project Co-Leader =A0 =A0 =A0 =A0 =A0cygwin AT cygwin DOT com
> Red Hat
>
> --
> Unsubscribe info: =A0 =A0 =A0http://cygwin.com/ml/#unsubscribe-simple
> Problem reports: =A0 =A0 =A0 http://cygwin.com/problems.html
> Documentation: =A0 =A0 =A0 =A0 http://cygwin.com/docs.html
> FAQ: =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 http://cygwin.com/faq/
>
>

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

