From: Ken Brown <kbrown@cornell.edu>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Fork problems on master branch
Date: Sun, 23 Jun 2019 17:14:00 -0000 [thread overview]
Message-ID: <86194d13-5e61-bec7-f7ca-a96930918d3e@cornell.edu> (raw)
In-Reply-To: <87e7b7f9-e1e5-92f2-c036-961dcc8c06f0@cornell.edu>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 917 bytes --]
On 6/9/2019 12:51 PM, Ken Brown wrote:
> On 6/8/2019 3:44 PM, Ken Brown wrote:
>> 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.
For the record, I've just pushed what I think is a fix for this problem. (At
least I can't reproduce the problem any more.)
Ken
\x03B‹KCB”\x1c›Ø›\x19[H\x1c™\^[Ü\x1cΈ\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÜ\x1c›Ø›\x19[\Ëš\x1d^[[\x03B‘TNˆ\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÙ˜\KÃB‘^[ØÝ[Y[\x18]\x1a[ÛŽˆ\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÙ^[ØÜËš\x1d^[[\x03B•[œÝXœØÜšX™H\x1a[™›Îˆ\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÛ[\vÈÝ[œÝXœØÜšX™K\Ú[\^[\x19CBƒB
prev parent reply other threads:[~2019-06-23 17:14 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
2019-06-23 17:14 ` Ken Brown [this message]
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=86194d13-5e61-bec7-f7ca-a96930918d3e@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).