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 47D46385803E
Authentication-Results:	sourceware.org; dmarc=none (p=none dis=none)
	header.from=SystematicSw.ab.ca
Authentication-Results:	sourceware.org;
	spf=none smtp.mailfrom=systematicsw.ab.ca
X-Authority-Analysis:	v=2.4 cv=PbTsOwtd c=1 sm=1 tr=0 ts=6275593c
	a=oHm12aVswOWz6TMtn9zYKg==:117 a=oHm12aVswOWz6TMtn9zYKg==:17
	a=IkcTkHD0fZMA:10 a=w_pzkKWiAAAA:8 a=MrylxDkSAAAA:8 a=94nOnFI1EgyDtX4ev68A:9
	a=QEXdDO2ut3YA:10 a=8oG9185d4NgA:10 a=sRI3_1zDfAgwuvI8zelB:22
	a=ZWqyT8odc8aVHPXL_V4W:22
Message-ID:	<7c6c793d-2997-e147-641f-d42fe4050e36@SystematicSw.ab.ca>
Date:	Fri, 6 May 2022 11:22:03 -0600
MIME-Version:	1.0
User-Agent:	Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
	Thunderbird/91.9.0
Subject:	Re: mintty crashes on Windows 7
To:	cygwin AT cygwin DOT com
References:	<CAGHpTB+t+gCySabZZQvJstZSLresmoOTUUL8of9cwCdvmGySdg AT mail DOT gmail DOT com>
	<20220504002343 DOT 4345bfe1630fa904276f0d37 AT nifty DOT ne DOT jp>
	<CAGHpTB+3V98eWDaHv7DCa133KWS39FaDFMUo=8qOJjxTFon51A AT mail DOT gmail DOT com>
	<20220504011018 DOT 7c455cedb38571f786d72ae9 AT nifty DOT ne DOT jp>
	<CAGHpTBJyOgYAzEvs3NLb8AzkiujbCKjaf+w-QSJAou47g-J-Cg AT mail DOT gmail DOT com>
	<CAGHpTB+tZX+z0ZkCNG-42bp4Pw+YKUXkccnnNqwN_tHRekk=UA AT mail DOT gmail DOT com>
	<20220504201610 DOT 125888f234ffe063fa6773c0 AT nifty DOT ne DOT jp>
	<CAGHpTBKphe_jSRS+9ihygODYGYYyzPfLPkt9H4rTDm9u7pMexw AT mail DOT gmail DOT com>
	<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>
	<CAGHpTBJRbqTf_2rmXD8413940+At+KS6_2C_702xR0t-L7aVSg AT mail DOT gmail DOT com>
From:	Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>
Organization:	Systematic Software
In-Reply-To:	<CAGHpTBJRbqTf_2rmXD8413940+At+KS6_2C_702xR0t-L7aVSg@mail.gmail.com>
X-CMAE-Envelope:	MS4xfGCqXdtW8ehoTt9TJtr2Bj88or98vyjAABYMGVMs1uvSSYu2FLLRHF6sSqK95dyT8vhW1i8/igYsAIMldeDKwgR71bFtyImSOsiiuAFWPkQCv+H5UUU3
	9MciMF766w2+/FvioeW8zi4X8THPKvquLzZ6xD5NpmRFq3j1EbjzWmJ9wQcCYS1dIwG6qFnjHqGO8IWWxUCjIhKGzwAR0rAnUdw=
X-Spam-Status:	No, score=-1165.2 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS,
	KAM_LAZY_DOMAIN_SECURITY, KAM_NUMSUBJECT, NICE_REPLY_A, SPF_HELO_NONE,
	SPF_NONE, 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
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe:	<https://cygwin.com/mailman/options/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<https://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
Reply-To:	cygwin AT cygwin DOT com
Errors-To:	cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com
Sender:	"Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>

On 2022-05-06 08:05, 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?
> Do you suggest that there's a bug in readline, that your change in the
> runtime uncovered? Or is it the other way around?
> What might we break if we revert the part I referenced earlier in
> fhandler_tty.cc?

Cygwin bash and other packages use the latest readline 8.1 library package:

	$ cygstart https://cygwin.com/packages/summary/readline-src.html

	$ cygcheck -l libreadline7
	/usr/bin/cygreadline7.dll
	/usr/bin/cyghistory7.dll

What readline does MSYS2 bash use - it requires libreadline-devel to 
build, but does not have any readline dependency, nor is libreadline 
required by bash:

	https://packages.msys2.org/package/bash
	https://packages.msys2.org/package/libreadline


-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]

-- 
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

- Raw text -