From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: many cygwin shells/tools (tcsh, fish, bash, and zsh) crashing STATUS_ACCESS_VIOLATION
Date: Tue, 10 Aug 2021 11:56:13 -0600 [thread overview]
Message-ID: <6cfbde9b-16ff-5de0-a040-8dcfb5d54bc3@SystematicSw.ab.ca> (raw)
In-Reply-To: <CAJtSMgvHBPUxZ_WZ+_QTABj06XsOxdexrKEkhV7kRZ+-zB7u+w@mail.gmail.com>
On 2021-08-10 08:20, David Dyck via Cygwin wrote:> On Mon, Aug 9, 2021
at 11:09 PM Brian Inglis wrote:
>>>>> Microsoft Windows [Version 10.0.22000.120]
>> You may also want to check your Windows Preview release docs, and
>> articles about it, for features such as address changes or randomization
>> (e.g. ASLR) being experimentally enabled on some % of systems, or
>> mandated, and applied to dlls, which will break Cygwin.
>
> thank you, I'll try to dig into the Windows Preview notes - as this
> doesn't happen on the work laptop
Apparently that Windows Version is for the Windows 11 Preview.
That appears to be an alpha quality product, from bug fix announcements.
I didn't find anything much useful from MS or articles only features.
You might want to reach out for help via the Windows Feedback Hub,
and/or MS App Assure re compatibility if your org has 150+ licenses.
--
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.]
next prev parent reply other threads:[~2021-08-10 17:56 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 [this message]
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
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=6cfbde9b-16ff-5de0-a040-8dcfb5d54bc3@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@cygwin.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).