From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Orgad Shaneh <orgads@gmail.com>
Cc: Takashi Yano <takashi.yano@nifty.ne.jp>, cygwin@cygwin.com
Subject: Re: mintty crashes on Windows 7
Date: Fri, 6 May 2022 21:16:10 +0200 (CEST) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.2205062109380.346@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <CAGHpTBJRbqTf_2rmXD8413940+At+KS6_2C_702xR0t-L7aVSg@mail.gmail.com>
Hi Orgad,
On Fri, 6 May 2022, Orgad Shaneh wrote:
> Adding @Johannes Schindelin to the loop.
Thank you, but that unfortunately does not work on this list. Due to the
policy to never reply-to-all, the subsequent replies immediately lost me.
The reason why MSYS2's Bash does not depend on the `libreadline` package
is that `bash.exe` is linked _statically_ to that library.
Takashi, for the record, I find it hard to believe that the bug is
libreadline's because Orgad's scenario works if he reverts that patch in
the _MSYS2 runtime_, _and_ it is rather dubious that libreadline would
potentially do anything that makes a call to `GetProcessWindowStation()`
not fail but _crash_.
These console patches sure are gifts that keep on giving.
Ciao,
Dscho
next prev parent reply other threads:[~2022-05-06 19:16 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
2022-05-06 17:22 ` Brian Inglis
2022-05-06 19:02 ` Takashi Yano
2022-05-06 19:16 ` Johannes Schindelin [this message]
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=nycvar.QRO.7.76.6.2205062109380.346@tvgsbejvaqbjf.bet \
--to=johannes.schindelin@gmx.de \
--cc=cygwin@cygwin.com \
--cc=orgads@gmail.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).