From: Orgad Shaneh <orgads@gmail.com>
To: Takashi Yano <takashi.yano@nifty.ne.jp>
Cc: cygwin@cygwin.com, Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: mintty crashes on Windows 7
Date: Fri, 6 May 2022 17:05:02 +0300 [thread overview]
Message-ID: <CAGHpTBJRbqTf_2rmXD8413940+At+KS6_2C_702xR0t-L7aVSg@mail.gmail.com> (raw)
In-Reply-To: <20220506074851.3ce94db7a3ab2bedf7e07f93@nifty.ne.jp>
On Fri, May 6, 2022 at 1:49 AM Takashi Yano <takashi.yano@nifty.ne.jp> 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?
- Orgad
next prev parent reply other threads:[~2022-05-06 14:05 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
2022-05-06 14:05 ` Orgad Shaneh [this message]
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=CAGHpTBJRbqTf_2rmXD8413940+At+KS6_2C_702xR0t-L7aVSg@mail.gmail.com \
--to=orgads@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=cygwin@cygwin.com \
--cc=takashi.yano@nifty.ne.jp \
/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).