X-Recipient: archive-cygwin AT delorie DOT com
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 7E30C385842B
Authentication-Results: sourceware.org;
 dmarc=none (p=none dis=none) header.from=maxrnd.com
Authentication-Results: sourceware.org; spf=none smtp.mailfrom=maxrnd.com
Subject: Re: many cygwin shells/tools (tcsh, fish, bash, and zsh) crashing
 STATUS_ACCESS_VIOLATION
To: cygwin AT cygwin DOT com
References: <CAJtSMguEyZ=cyVrfigEnBVM1JdRG04sk4A=nxh6+W6w_ZvbuQw AT mail DOT gmail DOT com>
 <0a68361c-0bca-c2d0-e122-ede519e03e01 AT SystematicSw DOT ab DOT ca>
 <CAJtSMguC=gPdA=EUj0Gf=in6GA52EY6M9R4_F7=fARR9Mb6LAw AT mail DOT gmail DOT com>
 <c4b69d0f-89c9-c9b6-097a-9ad91a449e25 AT SystematicSw DOT ab DOT ca>
 <CAJtSMgvHBPUxZ_WZ+_QTABj06XsOxdexrKEkhV7kRZ+-zB7u+w AT mail DOT gmail DOT com>
 <6cfbde9b-16ff-5de0-a040-8dcfb5d54bc3 AT SystematicSw DOT ab DOT ca>
 <CAJtSMgukBj0uwB3fY9+JzshQLJmgbOv1NiishNC8BuPwYW4S3Q AT mail DOT gmail DOT com>
From: Mark Geisert <mark AT maxrnd DOT com>
Message-ID: <3b947ca2-d86d-90f7-1270-2796e55bbbd6@maxrnd.com>
Date: Tue, 10 Aug 2021 12:49:14 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101
 Firefox/52.0 SeaMonkey/2.49.4
MIME-Version: 1.0
In-Reply-To: <CAJtSMgukBj0uwB3fY9+JzshQLJmgbOv1NiishNC8BuPwYW4S3Q@mail.gmail.com>
X-Spam-Status: No, score=-3.9 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS,
 KAM_LAZY_DOMAIN_SECURITY, NICE_REPLY_A, SPF_HELO_NONE, SPF_NONE,
 TXREP autolearn=no autolearn_force=no version=3.4.4
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on
 server2.sourceware.org
X-BeenThere: cygwin AT cygwin DOT com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe: <https://cygwin.com/mailman/options/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>

Hi David,

David Dyck via Cygwin wrote:
> On Tue, Aug 10, 2021 at 10:56 AM Brian Inglis  wrote:
>> 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.
> 
> I'm interested in what could be going wrong that would cause only some
> cygwin programs to fail.
> 
> I'd be happy to report the issue via Windows Feedback if I could point
> to something specific.
> 
> Maybe I should rebuild "more.exe" from source?

Won't help.  The strace and ldd output shows the exception is happening in 
cygncursesw-10.dll.  That's unfortunate because many Cygwin programs use that DLL, 
including the debugger gdb.

> comparing the mentioned
>    more.exe.stackdump
> and
>     bash.exe.stackdump
> it appears that cygwin creates different formats of files but seems to
> call them *.stackdump

Yes, that's intentional.  Depending on the current state of the faulting program 
it may not be possible to get a stack backtrace.  The info shown is what can 
(probably) be trusted.

You could try downgrading ncurses via Cygwin setup.  Best case: things work. 
Worst case: things break but at a different address within the DLL.

Another tack could be for somebody *on a working system* install the debuginfo for 
ncurses, figure out the exception's address *in the ncurses installed locally*, 
run 'more' under gdb after setting a breakpoint at that address.  Poke around to 
see what ncurses is doing in that area.  Maybe it's acting on a Windows result 
that's busted on the Windows preview.  Or something else.  Good luck with this 
route :-/.

..mark

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple