public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Fork problems on master branch
Date: Sun, 09 Jun 2019 16:51:00 -0000	[thread overview]
Message-ID: <87e7b7f9-e1e5-92f2-c036-961dcc8c06f0@cornell.edu> (raw)
In-Reply-To: <330c76fd-af22-beb9-08b6-707c73df3b75@cornell.edu>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1666 bytes --]

On 6/8/2019 3:44 PM, Ken Brown wrote:
> Earlier today I reported on the cygwin-patches list a fork problem with a
> cygwin1.dll built from the master branch of the Cygwin source repo.  See
> https://cygwin.com/ml/cygwin-patches/2019-q2/msg00155.html.  A bisection showed
> that commit f03ea8e1 was the first bad commit for the problem being discussed there.
> 
> I've just run into a second fork problem for which I think the same commit is
> the first bad one.  I can't be positive, because the problem is sporadic, so I
> might have marked some bad commits as good if I didn't run the test enough times.
> 
> The test case for this (attached) is one that I used when testing my new FIFO
> code.  Normally I run this program in one terminal and type
> 
>     echo blah > /tmp/myfifo
> 
> in a second terminal.  For the present purposes, however, you can skip the
> second part and simply terminate fifo_fork_test with C-c.
> 
> In my testing, I found that running the test program would yield "read: Bad
> address" about 1 out of 10 times.  Occasionally I would get "read: Communication
> error on send" instead.  Both error messages indicate a problem with the child
> process reading from an fd inherited from the parent.

Never mind.  This seems to be a bug in my recently added FIFO code.  I just 
never before ran my test many times in a row, so I never saw the error before.

Sorry for the noise.

Ken
\0ТÒÐÐ¥\a&ö&ÆVÒ\a&W\x06÷'G3¢\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒ÷\a&ö&ÆV×2æ‡FÖÀФd\x15\x13¢\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöf\x17\x12ðФFö7VÖVçF\x17F–öã¢\x02\x02\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöFö72æ‡FÖÀÐ¥Vç7V'67&–&R\x06–æfó¢\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöÖÂò7Vç7V'67&–&R×6–×\x06ÆPРÐ

  reply	other threads:[~2019-06-09 16:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-08 19:44 Ken Brown
2019-06-09 16:51 ` Ken Brown [this message]
2019-06-23 17:14   ` Ken Brown

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=87e7b7f9-e1e5-92f2-c036-961dcc8c06f0@cornell.edu \
    --to=kbrown@cornell.edu \
    --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).