public inbox for
 help / color / mirror / Atom feed
From: Thomas Wolff <>
Subject: Re: [PATCH] Cygwin: pty: Fix segfault caused when tcflush() is called.
Date: Tue, 23 Feb 2021 12:24:09 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Am 22.02.2021 um 14:57 schrieb Corinna Vinschen via Cygwin-patches:
> On Feb 22 20:41, Takashi Yano via Cygwin-patches wrote:
>> On Mon, 22 Feb 2021 10:51:19 +0100
>> Corinna Vinschen wrote:
>>> So, what do you think is the state of the console code, Takashi?
>>> Shall we start a release cycle next week?
>> I think all the fixes and improvements that come to mind at this
>> point have been completed. As for releasing, I believe I've done
>> enough testing, but honestly I'm not without anxiety because total
>> amount of changes for pty and console code is relatively large
>> since the beginning of this year.
>> On the other hand, I also want people to use new features as soon
>> as possible.
> Then let's do it.  I'll start with the usual test releases...
I've downloaded yesterday's snapshot (2021-02-22) for some testing.
If I compile mintty (which passes without problem) and try to run it, it 
just exits silently (no window popped up).
After reverting to 3.1.7, it runs just fine (even the one compiled with 
the snapshot).

  reply	other threads:[~2021-02-23 11:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-20 22:45 Takashi Yano
2021-02-22  9:51 ` Corinna Vinschen
2021-02-22 11:41   ` Takashi Yano
2021-02-22 13:28     ` Takashi Yano
2021-02-22 13:57       ` Corinna Vinschen
2021-02-22 13:57     ` Corinna Vinschen
2021-02-23 11:24       ` Thomas Wolff [this message]
2021-02-23 13:13         ` Takashi Yano
2021-02-23 13:33           ` Takashi Yano
2021-02-23 17:15             ` Thomas Wolff

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).