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:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=ywvG8YJddx78ZuOh
	AtahCDTzvTNuG0wEYRuGH3Zey8sTGRTdifC9+EgQ8cuscHefwS3yaWjHx6GJ6M52
	LiszsclxH9tuMiKh7TPtP152vKiO8Pu2KJRfDlmuq9LCJS67tey7VCKzuuXIhnUh
	hzejhJ0CDtndo5LHYTegPrm0BVw=
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:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=xbzkZv5hL78tE9L+8obAVf
	oRwV0=; b=D9Qu02RZlWv4AJy/4daBjZ1hMLIEnjV6tXMGxra/Z2GJcrKUgHa6zt
	RjRX4N7BcmLe1DBGd7PE0iP3UOMW+zx7heuSXlZX4Fbu1E9oYnX2o78vvJkJpEX6
	zK5sgywyGSjcZ9d8OCtkSMjMKSGSVgatXTe3QUTLm/VoLK5VuD7+0=
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=2.9 required=5.0 tests=BAYES_50,KAM_COUK,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE autolearn=no version=3.3.2
X-HELO:	smtpout.wanadoo.co.uk
X-ME-Helo:	[192.168.15.105]
X-ME-Auth:	ZHdhbGluQGZzbmV0LmNvLnVr
X-ME-Date:	Tue, 08 Sep 2015 06:40:59 +0200
X-ME-IP:	85.210.49.154
Subject:	Re: Question about flock - potential memory corruption?
To:	cygwin AT cygwin DOT com
References:	<CALd+sZRo_Nyv=adF5DeeHiShJsxGD+KUPqkDMKb3q47a2Nm=8Q AT mail DOT gmail DOT com> <CALd+sZSUAt6_fdHkgdKqefz1Wv-ijShSo82qJKUcCkZH9v5KzA AT mail DOT gmail DOT com> <CALd+sZQUy=Yn6UJ74N4Bvxd_wi++v+kOU5MehAkW7oaLO+NVbw AT mail DOT gmail DOT com>
From:	Sam Edge <sam DOT edge AT dwalin DOT fsnet DOT co DOT uk>
X-Enigmail-Draft-Status:	N1110
Message-ID:	<55EE66E1.3000908@dwalin.fsnet.co.uk>
Date:	Tue, 8 Sep 2015 05:41:05 +0100
User-Agent:	Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version:	1.0
In-Reply-To:	<CALd+sZQUy=Yn6UJ74N4Bvxd_wi++v+kOU5MehAkW7oaLO+NVbw@mail.gmail.com>

On 07/09/2015 19:45, Qian Hong wrote:
> Hi,
>
> Attach is the simple test case I use to reproduce the valgrind warning
> and random failures.
>
> Compile the test case in Cygwin with below command line:
> $ gcc -g -O0 flock.c -o flock.exe
>
> Thanks!
>
Hi,

Erm ... slight technical hitch? Your example flock.c doesn't call
fork(), nor does it use your two macros MAX_ITER & CHILDREN.

-- 
Sam Edge

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

- Raw text -