From: Sam Edge <sam.edge@dwalin.fsnet.co.uk>
To: cygwin@cygwin.com
Subject: Re: Question about flock - potential memory corruption?
Date: Tue, 08 Sep 2015 04:41:00 -0000 [thread overview]
Message-ID: <55EE66E1.3000908@dwalin.fsnet.co.uk> (raw)
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
next prev parent reply other threads:[~2015-09-08 4:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-04 20:22 Qian Hong
2015-09-07 18:42 ` Qian Hong
2015-09-07 18:46 ` Qian Hong
2015-09-08 4:41 ` Sam Edge [this message]
2015-09-08 5:54 ` Qian Hong
2015-09-08 8:58 ` Corinna Vinschen
2015-09-08 10:36 ` Qian Hong
2015-09-08 15:31 ` Corinna Vinschen
2015-09-08 15:54 ` Qian Hong
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=55EE66E1.3000908@dwalin.fsnet.co.uk \
--to=sam.edge@dwalin.fsnet.co.uk \
--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).