This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Question about flock - potential memory corruption?
- From: Sam Edge <sam dot edge at dwalin dot fsnet dot co dot uk>
- To: cygwin at cygwin dot com
- Date: Tue, 8 Sep 2015 05:41:05 +0100
- Subject: Re: Question about flock - potential memory corruption?
- Authentication-results: sourceware.org; auth=none
- 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>
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