public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: 3.3.0: Possible regression in cygwin DLL (Win10); fixed in snapshot
Date: Fri, 5 Nov 2021 16:08:31 -0400	[thread overview]
Message-ID: <2cfa5de7-3b95-9062-4572-f36d304bc916@cornell.edu> (raw)
In-Reply-To: <20211106044116.698b465a5d8ed6ce2cc75c99@nifty.ne.jp>

Hi Takashi,

On 11/5/2021 3:41 PM, Takashi Yano via Cygwin wrote:
> Thanks much for the detailed steps. I could reproduce the problem.
> 
> It seems that the cause is the overhaul for the pipe implementation.
> I also found the workaround for this issue. Please try:
> export CYGWIN=pipe_byte
> 
> Corinna, Ken,
> What about setting pipe mode to byte by default?

I have a vague recollection that this caused some other problem, but I'll have 
to review the email discussions from a few months ago.  I'm traveling at the 
moment and won't get to this for a few days.

In the meantime, could you explain (probably on cygwin-developers) why message 
mode causes the reported issue?  Also, does the problem occur only when there 
are non-Cygwin apps involved?

Thanks.

Ken

  reply	other threads:[~2021-11-05 20:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-04 15:02 Brian
2021-11-05  3:39 ` Takashi Yano
     [not found]   ` <CAEv6GOA-y58YrftXgEgFrjqtOTHmfdu2Vrq76Lwn0suZpZ=U9w@mail.gmail.com>
2021-11-05  8:05     ` Takashi Yano
2021-11-05 13:42       ` Brian
2021-11-05 19:41         ` Takashi Yano
2021-11-05 20:08           ` Ken Brown [this message]
2021-11-06 16:22             ` Ken Brown
2021-11-05 21:32           ` Brian
2021-11-06  6:24         ` ASSI
2021-11-08 16:30           ` Andrey Repin
2021-11-08 20:49             ` Adam Dinwoodie
2021-11-08 23:18               ` Brian Koontz

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=2cfa5de7-3b95-9062-4572-f36d304bc916@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).