From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: 2.3.0: possible Cygwin flock bug (Windows 10 x86_64)
Date: Thu, 12 Nov 2015 12:28:00 -0000 [thread overview]
Message-ID: <20151112122809.GB1774@calimero.vinschen.de> (raw)
In-Reply-To: <CACnvoQfd04snMS5OHu_WuqH+csXBWvXwUCutip9xZb6Hvi9ueg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1399 bytes --]
Hi Mario,
On Nov 11 21:51, Mario Roy wrote:
> Greetings,
>
> During testing of the Perl MCE 1.608 module (uses flock), the examples
> scripts hang. Downgrading the base Cygwin package from 2.3.0-1 to
> 2.2.1-1 resolves the issue.
>
> Installation is not required if a Cygwin developer desires to test
> file locking via the Perl MCE module.
>
> https://cpan.metacpan.org/authors/id/M/MA/MARIOROY/MCE-1.608.tar.gz
>
> 1. extract tar file
> 2. cd MCE-1.608/examples
> 3. perl foreach.pl 10
>
> Hangs with Cygwin 2.3.0-1
> Successful with Cygwin 2.2.1-1
Thanks for the testcase. I found the problem. In 2.2.1 was a
use-after-free bug in the file locking code which I fixed in
2.3.0... just wrongly. It fails to work in certain cases when
locking collisions occur. I fixed this in the git repo.
I uploaded a new developer snapshot to https://cygwin.com/snapshots/
Please give it a try.
> The upcoming Perl MCE 1.7 release does away with file locking and
> works with 2.3.0-1.
Uh, please don't do this. This is a bug in Cygwin 2.3.0, and the right
fix is to release Cygwin 2.3.1 end of this week, not to change other
packages to workaround this bug.
> p.s. Thank you for Cygwin
Thanks :)
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-11-12 12:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 2:51 Mario Roy
2015-11-12 12:28 ` Corinna Vinschen [this message]
2015-11-13 18:25 ` Mario Roy
2015-11-16 11:24 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151112122809.GB1774@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).