DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 47D46385803E
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
Content-Language: en-CA
To: cygwin@cygwin.com
References: <CAGHpTB+t+gCySabZZQvJstZSLresmoOTUUL8of9cwCdvmGySdg@mail.gmail.com>
 <20220504002343.4345bfe1630fa904276f0d37@nifty.ne.jp>
 <CAGHpTB+3V98eWDaHv7DCa133KWS39FaDFMUo=8qOJjxTFon51A@mail.gmail.com>
 <20220504011018.7c455cedb38571f786d72ae9@nifty.ne.jp>
 <CAGHpTBJyOgYAzEvs3NLb8AzkiujbCKjaf+w-QSJAou47g-J-Cg@mail.gmail.com>
 <CAGHpTB+tZX+z0ZkCNG-42bp4Pw+YKUXkccnnNqwN_tHRekk=UA@mail.gmail.com>
 <20220504201610.125888f234ffe063fa6773c0@nifty.ne.jp>
 <CAGHpTBKphe_jSRS+9ihygODYGYYyzPfLPkt9H4rTDm9u7pMexw@mail.gmail.com>
 <20220505102045.fd6bfd46732e2eab0451e28c@nifty.ne.jp>
 <20220505102724.11b5675450f2b4f723a8b70e@nifty.ne.jp>
 <20220505105954.e910df2e6998d130a9373299@nifty.ne.jp>
 <20220505123307.e745d7c88877316b9a38d0c9@nifty.ne.jp>
 <20220505134120.242af45a631131d7e4217f5e@nifty.ne.jp>
 <20220505154440.d9002cc94e7d52b3c6c1f339@nifty.ne.jp>
 <20220506074851.3ce94db7a3ab2bedf7e07f93@nifty.ne.jp>
 <CAGHpTBJRbqTf_2rmXD8413940+At+KS6_2C_702xR0t-L7aVSg@mail.gmail.com>
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
Organization: Systematic Software
In-Reply-To: <CAGHpTBJRbqTf_2rmXD8413940+At+KS6_2C_702xR0t-L7aVSg@mail.gmail.com>
Precedence: list
Reply-To: cygwin@cygwin.com
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: cygwin-bounces+archive-cygwin=delorie.com@cygwin.com
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie.com@cygwin.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