X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=gVIRaY6yunarImqnSaVpdo3mPcxphbXFZwctl3oSHEkvf+2xhE3oe
	yLWSeIp9yM+7nnXUElmeNhliMTQPdUXOcZOuqf/Toe0uXK7mXcazgkdd6i9ORpsm
	kub+QhTI1r1Yym9F6fLNMRNUgjjHf+pWXFvJ3vkECFJgiCI1AeV1jY=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	 bh=+XJeJQ0jtX1PFGAY/ihbT7FTyZ0=; b=wKO15q5AFoo4ZL829ACAKvqo1U7S
	WfVCecageyqTucT4wI3o6uB3mREe4k6KBclVhEzyMvco9Q1y6E43QpVSvV1I/Bvs
	wFK2O65zbkbh9hb2mFPPO0NxqtOHs8cYWpg6zjptLHHg6tliZri565/OqPSKEhcN
	rt5dDP6nCGGsXwE=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-4.1 required=5.0 tests=AWL,BAYES_50,KAM_LAZY_DOMAIN_SECURITY autolearn=no version=3.3.2
X-HELO: calimero.vinschen.de
Date: Tue, 8 Sep 2015 17:31:33 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Question about flock - potential memory corruption?
Message-ID: <20150908153133.GA4252@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <CALd+sZRo_Nyv=adF5DeeHiShJsxGD+KUPqkDMKb3q47a2Nm=8Q AT mail DOT gmail DOT com> <20150908085854 DOT GB24811 AT calimero DOT vinschen DOT de> <CALd+sZTCJPw2=NObcZ6-522C=yXZ8xiix69dEy2BsAEWUyG7qA AT mail DOT gmail DOT com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;	protocol="application/pgp-signature"; boundary="0OAP2g/MAC+5xKAE"
Content-Disposition: inline
In-Reply-To: <CALd+sZTCJPw2=NObcZ6-522C=yXZ8xiix69dEy2BsAEWUyG7qA@mail.gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)

--0OAP2g/MAC+5xKAE
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sep  8 18:35, Qian Hong wrote:
> Hi Corinna,
>=20
> Thanks a lot for your time.
>=20
> On Tue, Sep 8, 2015 at 4:58 PM, Corinna Vinschen
> <corinna-cygwin AT cygwin DOT com> wrote:
>=20
> > I'd still be glad to stick to upstream Cygwin, but, oh well.
> Understand, will take care of that.
>=20
>=20
> > Please try the attached patch.
> Thanks a lot for the patch, I can confirm it works for me, flock()
> doesn't fail on Wine anymore. Also, valgrind doesn't report the
> previous warnings.
>=20
> Once you have snapshot build I'm glad to retest.

Snapshot is up.


Thanks,
Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--0OAP2g/MAC+5xKAE
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJV7v9VAAoJEPU2Bp2uRE+gzcYP/A87MFjhrMs2P1c0xGrM6Dqt
n28jRqPDR/gOX73IXbzUE3UbUpoyxZ7ms7F8zDlO5C2T8Ji4JYtCzcNdH7xJw8HI
vp5B6he9ncWnJtNYF54bN0CTtT/orZswvWHWN/Uconminu1iR7UikiJxcWhphddQ
ywYMBi82g/yKQewtNo9dG9NNTzn+a/w2/WQF/fWhqOMVgJfHpu5I17jrMYc3Tb6T
8VJ+dhagg1VuaNVWqoQCrFP6IHGaxwkmioBUJna/y4Sjd+LRlMHaclfKbLFY2n0O
7zhPUpZUpoDYQbQxMf37NaIWiQOef9q0QjHdH1fCewZFKcbt3vSnRn0KxonUFbcN
uwmF6h9Lvh4EmrqLZ+CTxO0tgxmCR7cHkfSV+g6rPQp6w59wIO03X8r0P5PfqHyD
xnUm8fRlC+oTmpHvuAGbsg98HMR49/GplKf/WqVWWpQ/JcNdvh0ojTybDdRkqMBg
uEFKhMOWxHLpDvl7/R1lZgcKWT+cCyT5/hldyDzSdyT4kiemEGKNusBpAyeaPIPT
/Z2nWxi3n6KwzNYPjbV50rtJsIALOym0PC2UaOHAz9fRYuWyY6Mz458i7z+qha+4
oRBxvzK+i14ZexmqeRzrycV5zMyzNBDhWb06BRHTQbcPBSaiGSIDbi7NdhGkM1KV
ctwTwhAfracVYi0+TbXw
=ntMw
-----END PGP SIGNATURE-----

--0OAP2g/MAC+5xKAE--