From: Thomas Wolff <towo@towo.net>
To: cygwin-patches@cygwin.com
Subject: Re: [PATCH] Cygwin: pty: Fix segfault caused when tcflush() is called.
Date: Tue, 23 Feb 2021 18:15:12 +0100 [thread overview]
Message-ID: <a361d770-0ef6-0e02-2bc2-9c2758d6116a@towo.net> (raw)
In-Reply-To: <20210223223358.96ba58e9d805b6f0caf3cf4b@nifty.ne.jp>
Am 23.02.2021 um 14:33 schrieb Takashi Yano via Cygwin-patches:
> On Tue, 23 Feb 2021 22:13:52 +0900
> Takashi Yano wrote:
>> Hi Thomas,
>>
>> On Tue, 23 Feb 2021 12:24:09 +0100
>> Thomas Wolff wrote:
>>> 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).
>> Thanks for testing. However, I cannot reproduce your problem.
>> I downloaded mintty-3.4.6-1-src.tar.xz and extract it.
>> Then run
>> cygport mintty-3.4.6-1.cygport prep
>> cygport mintty-3.4.6-1.cygport compile
>>
>> The binary in build/bin directory works with cygwin snapshot
>> 2021-02-22. I have tried both 32bit and 64bit build, and both
>> work without problem.
>>
>> Could you please provide some more information?
> Difference of compiler version?
> I am using gcc-g++ 10.2.0-1.
Apologies, I confused this. I *wanted* to try the snapshot but then
tried a self-compiled dll instead (fresh git pull).
The snapshot works. The git pull doesn't but that may have other
mysterious reasons.
Thomas
prev parent reply other threads:[~2021-02-23 17:15 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
2021-02-23 13:13 ` Takashi Yano
2021-02-23 13:33 ` Takashi Yano
2021-02-23 17:15 ` Thomas Wolff [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=a361d770-0ef6-0e02-2bc2-9c2758d6116a@towo.net \
--to=towo@towo.net \
--cc=cygwin-patches@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).