IPC,FORK on Windows 2008 Server

Yarlagadda Suresh ysuresh.forum@gmail.com
Wed Apr 1 05:49:00 GMT 2009


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.   Unfortunately I can still reproduce the problem once per
>> about 30 forks.
>>
>> I'll look into fixing this for Cygwin 1.7.  However, please note that
>> there is no *really* foolproof method to fix this due to the way fork
>> has to be implemented using Win32 calls.  I 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.  This should make the
> observed effect at fork() pretty unlikely.  The patch will be in the
> next Cygwin 1.7.0 test release (in a couple of days).
>
>
> Thanks for the report,
> Corinna
>
> --
> Corinna Vinschen                  Please, send mails regarding Cygwin to
> Cygwin Project Co-Leader          cygwin AT cygwin DOT com
> Red Hat
>
> --
> 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/
>
>

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



More information about the Cygwin mailing list