From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Cc: Orgad Shaneh <orgads@gmail.com>
Subject: Re: mintty crashes on Windows 7
Date: Fri, 6 May 2022 07:48:51 +0900 [thread overview]
Message-ID: <20220506074851.3ce94db7a3ab2bedf7e07f93@nifty.ne.jp> (raw)
In-Reply-To: <20220505154440.d9002cc94e7d52b3c6c1f339@nifty.ne.jp>
On Thu, 5 May 2022 15:44:40 +0900
Takashi Yano wrote:
> On Thu, 5 May 2022 13:41:20 +0900
> Takashi Yano wrote:
> > I downloaded bash source files from:
> > https://git.savannah.gnu.org/git/bash.git
> > and built it by:
> > ./configure && make
> > and replaced /usr/bin/bash.
> >
> > Then the issue disappeared.
> > Now, I start to suspect the issue is a bug of msys2 bash package.
>
> I tried several shells and results are as follows.
>
> tcsh: ok
> ash: ok
> dash: ok
> zsh: ok
> ksh: ok
> fish: ok
> bash (build from original source): ok
>
> bash (from msys2 package): ng
>
> 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.
--
Takashi Yano <takashi.yano@nifty.ne.jp>
next prev parent reply other threads:[~2022-05-05 22:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 11:47 Orgad Shaneh
2022-05-03 15:23 ` Takashi Yano
2022-05-03 15:52 ` Orgad Shaneh
2022-05-03 16:10 ` Takashi Yano
2022-05-04 9:33 ` Orgad Shaneh
2022-05-04 9:46 ` Orgad Shaneh
2022-05-04 11:16 ` Takashi Yano
2022-05-04 13:27 ` Orgad Shaneh
2022-05-05 1:20 ` Takashi Yano
2022-05-05 1:27 ` Takashi Yano
2022-05-05 1:59 ` Takashi Yano
2022-05-05 3:33 ` Takashi Yano
2022-05-05 4:41 ` Takashi Yano
2022-05-05 6:44 ` Takashi Yano
2022-05-05 22:48 ` Takashi Yano [this message]
2022-05-06 14:05 ` Orgad Shaneh
2022-05-06 17:22 ` Brian Inglis
2022-05-06 19:02 ` Takashi Yano
2022-05-06 19:16 ` Johannes Schindelin
2022-05-06 20:13 ` Takashi Yano
2022-05-07 0:20 ` Takashi Yano
2022-05-08 11:08 ` Takashi Yano
2022-05-08 11:22 ` Orgad Shaneh
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=20220506074851.3ce94db7a3ab2bedf7e07f93@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--cc=cygwin@cygwin.com \
--cc=orgads@gmail.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).