X-Recipient: archive-cygwin AT delorie DOT com X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 2553D3858D28 Authentication-Results: sourceware.org; dmarc=fail (p=none dis=none) header.from=nifty.ne.jp Authentication-Results: sourceware.org; spf=fail smtp.mailfrom=nifty.ne.jp DKIM-Filter: OpenDKIM Filter v2.10.3 conssluserg-01.nifty.com 246J26gC021450 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nifty.ne.jp; s=dec2015msa; t=1651863727; bh=UrvbTeuzsH6/R2dONT4z2K4WIkq2KCWmz5V5DIh0oRc=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=cL6iRxK0xhMpe/x1Xna/oNu0NmUNOfzxaxuANVC9FRBn/lBr2xRVzSSfMEDJAULGj 4IET9DX8StgS9UMB1jiyylMa8XRS5yPvz3JaIAmKax+MoFCG/1SmIvqhXpSsqpPZPI j3CfxhzO0Qg2bAm//2b/ZGT6VqdSDJLdaN+VKyuk/SnOg3eHlsPz3VXcnYNHWaIont xCB1md5OCqYG8wMnu08AzKwt1xE3lZPPYs2Md/3G5lplBSLFFgIqftNJUt82XpY6bB 8jf1+d4ktxAljvM5KZn2TkmrSj2Ts1C5joz+l5bANPlVtfSlXAZGPiJ/+n95G59pnM 1o6b4yk1Ghplg== X-Nifty-SrcIP: [119.150.44.95] Date: Sat, 7 May 2022 04:02:11 +0900 From: Takashi Yano To: cygwin AT cygwin DOT com Subject: Re: mintty crashes on Windows 7 Message-Id: <20220507040211.77da7b5c285bc9ffe35f6bcf@nifty.ne.jp> In-Reply-To: References: <20220504002343 DOT 4345bfe1630fa904276f0d37 AT nifty DOT ne DOT jp> <20220504011018 DOT 7c455cedb38571f786d72ae9 AT nifty DOT ne DOT jp> <20220504201610 DOT 125888f234ffe063fa6773c0 AT nifty DOT ne DOT jp> <20220505102045 DOT fd6bfd46732e2eab0451e28c AT nifty DOT ne DOT jp> <20220505102724 DOT 11b5675450f2b4f723a8b70e AT nifty DOT ne DOT jp> <20220505105954 DOT e910df2e6998d130a9373299 AT nifty DOT ne DOT jp> <20220505123307 DOT e745d7c88877316b9a38d0c9 AT nifty DOT ne DOT jp> <20220505134120 DOT 242af45a631131d7e4217f5e AT nifty DOT ne DOT jp> <20220505154440 DOT d9002cc94e7d52b3c6c1f339 AT nifty DOT ne DOT jp> <20220506074851 DOT 3ce94db7a3ab2bedf7e07f93 AT nifty DOT ne DOT jp> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32) Mime-Version: 1.0 X-Spam-Status: No, score=-5.8 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, KAM_NUMSUBJECT, NICE_REPLY_A, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Johannes Schindelin , Orgad Shaneh Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com Sender: "Cygwin" On Fri, 6 May 2022 17:05:02 +0300 Orgad Shaneh wrote: > On Fri, May 6, 2022 at 1:49 AM Takashi Yano wrote: > > > Only bash in msys2 package fails. > > > > I identified the difference which causes the issue > > between bash built from original source and msys2 bash. > > > > If --enable-readline and --with-installed-readline is specified > > to configure, the problem causes even with bash built from original > > source. > > > > Also, removing --with-installed-readline from configure and removing > > READLINE_LDFLAGS= from make in PKGBUILD of MSYS2 bash package solves > > the issue. > > > > So it seems to be a readline problem, not a bug in bash itself. > > Adding @Johannes Schindelin to the loop. > > Thanks for your investigation so far. > > So how do we proceed, assuming MSYS project does want to use the > installed readline? I checked the readline PKGBUILD, and it only has > very basic patches, none of them looks suspicious. > > Is (external) readline not used in cygwin/bash? In cygwin the issue does not occur even with bash configured with --enable-readline and --with-installed-readline. > Do you suggest that there's a bug in readline, that your change in the > runtime uncovered? Or is it the other way around? I suspect it's the former. > What might we break if we revert the part I referenced earlier in > fhandler_tty.cc? If you revert that commit, non-cygwin app recieves ctrl-c twice in the following scenario. 1) Start mintty 2) Run cmd.exe 3) Run script command 4) Run non-cygwin app 5) Press ctrl-c This is becase ctrl-c is processed by both mintty pty master and script pty master. -- Takashi Yano -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple