From: David Dyck <david.dyck@gmail.com>
To: Takashi Yano <takashi.yano@nifty.ne.jp>
Cc: cygwin@cygwin.com
Subject: Re: many cygwin shells/tools (tcsh, fish, bash, and zsh) crashing STATUS_ACCESS_VIOLATION
Date: Mon, 9 Aug 2021 22:12:59 -0700 [thread overview]
Message-ID: <CAJtSMgvUAdSh8EENODig7jNuhNyiWE=GTh+fCpmFEt3ZsnB3dw@mail.gmail.com> (raw)
In-Reply-To: <20210810140752.fa6a245a2ba432855929f97f@nifty.ne.jp>
On Mon, Aug 9, 2021 at 10:08 PM Takashi Yano wrote:
>
> On Mon, 9 Aug 2021 21:36:15 -0700
> David Dyck wrote:
> > I've had it running for many years, but recently upgraded to windows 10
> > c:\cygwin64\bin>ver
> >
> > Microsoft Windows [Version 10.0.22000.120]
>
> This does not seem to be a version number of Windows10 but
> a version number of latest Windows11 insider preview.
>
> However, in my environment, cygwin works as expected in
> Windows11 insider prevew as well as Windows10.
Yes, you are correct, it is Windows 11 insider preview
and I have another computer that is also running Win 11 preview with
cygwin just fine.
I was surprised to have these exceptions on what used to be a reliable system.
prev parent reply other threads:[~2021-08-10 5:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-10 4:36 David Dyck
2021-08-10 5:04 ` Brian Inglis
2021-08-10 5:16 ` David Dyck
2021-08-10 6:08 ` Brian Inglis
2021-08-10 14:20 ` David Dyck
2021-08-10 17:56 ` Brian Inglis
2021-08-10 18:20 ` David Dyck
2021-08-10 19:49 ` Mark Geisert
2021-08-10 20:30 ` Doug Henderson
2021-08-11 4:38 ` David Dyck
2021-08-11 5:27 ` Mark Geisert
2021-08-11 14:25 ` David Dyck
2021-08-12 5:09 ` Mark Geisert
2021-08-12 5:22 ` David Dyck
2021-08-10 5:07 ` Takashi Yano
2021-08-10 5:12 ` David Dyck [this message]
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='CAJtSMgvUAdSh8EENODig7jNuhNyiWE=GTh+fCpmFEt3ZsnB3dw@mail.gmail.com' \
--to=david.dyck@gmail.com \
--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).