public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Subject: Re: Race condition hangs on multiple mintty/tcsh? Brad Wetmore
Date: Tue, 11 Aug 2020 19:02:00 +0900	[thread overview]
Message-ID: <20200811190200.cc385900e784c6cd076f53ba@nifty.ne.jp> (raw)
In-Reply-To: <20200811093758.GF53219@calimero.vinschen.de>

On Tue, 11 Aug 2020 11:37:58 +0200
Corinna Vinschen wrote:
> On Aug 11 13:59, Takashi Yano via Cygwin wrote:
> > Hi Thomas,
> > 
> > On Thu, 6 Aug 2020 15:31:24 +0200
> > Thomas Wolff wrote:
> > > Am 06.08.2020 um 13:46 schrieb Thomas Wolff:
> > > > Am 06.08.2020 um 01:23 schrieb Kevin Schnitzius via Cygwin:
> > > >> On Wednesday, August 5, 2020, 06:56:48 PM EDT, Thomas Wolff 
> > > >> <towo@towo.net> wrote:
> > > >>> Am 04.08.2020 um 12:02 schrieb Thomas Wolff:
> > > >>>> Am 04.08.2020 um 00:13 schrieb Brad Wetmore via Cygwin:
> > > >>>>> Hi,
> > > >>>>>
> > > >>>>> I generally kick off multiple (10) mintty sessions, and place them
> > > >>>>> around the screen.
> > > >>>>> [...]
> > > > I could reproduce one case of one of three terminals being 
> > > > unresponsive also with xterm.
> > > And it also happens if I drop select() from mintty (and use just 
> > > non-blocking read()).
> > > > Does anybody familiar with pty/select or recent changes have any idea?
> > 
> > I looked into this problem. After much struggle, I think
> > I have found a workaround for this issue.
> > 
> > I am not sure why this solves the issue at all, however,
> > this works for me.
> > 
> > Could you please test a patch attached?
> 
> Shall I commit the patch and create a developer snapshot for testing?

Thanks so much. That would be more convenient for potential testers.

-- 
Takashi Yano <takashi.yano@nifty.ne.jp>

  reply	other threads:[~2020-08-11 10:02 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-03 22:13 Brad Wetmore
2020-08-04 10:02 ` Thomas Wolff
2020-08-05 22:56   ` Thomas Wolff
2020-08-05 23:23     ` Kevin Schnitzius
2020-08-06 11:46       ` Thomas Wolff
2020-08-06 13:31         ` Thomas Wolff
2020-08-06 14:26           ` Corinna Vinschen
2020-08-06 14:33             ` Thomas Wolff
2020-08-07 15:34               ` Takashi Yano
2020-08-11  4:59           ` Takashi Yano
2020-08-11  9:37             ` Corinna Vinschen
2020-08-11 10:02               ` Takashi Yano [this message]
2020-08-11 10:30                 ` Corinna Vinschen
2020-08-11 17:37                   ` Thomas Wolff
2020-08-12 20:27                     ` Thomas Wolff
2020-08-06 18:07 ` Brad Wetmore
2020-08-06 18:48   ` Thomas Wolff
2020-08-06 19:25   ` Brad Wetmore
2020-08-13  3:08     ` Brad Wetmore
2020-08-25 18:45       ` Brad Wetmore

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=20200811190200.cc385900e784c6cd076f53ba@nifty.ne.jp \
    --to=takashi.yano@nifty.ne.jp \
    --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).