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 6A8363877407
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
Cc:	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>
	<3b947ca2-d86d-90f7-1270-2796e55bbbd6 AT maxrnd DOT com>
	<08cdda56-2994-ae30-d508-9491ad24422f AT maxrnd DOT com>
	<CAJtSMgtPPT_8BAoYq2NDzuwog1xNt6wGkis2J1dwJyTMgkaD9w AT mail DOT gmail DOT com>
From:	Mark Geisert <mark AT maxrnd DOT com>
Message-ID:	<e213df8d-e3c5-2818-aab7-7b30698c87b6@maxrnd.com>
Date:	Wed, 11 Aug 2021 22:09:23 -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:	<CAJtSMgtPPT_8BAoYq2NDzuwog1xNt6wGkis2J1dwJyTMgkaD9w@mail.gmail.com>
X-Spam-Status:	No, score=-1.0 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS,
	KAM_LAZY_DOMAIN_SECURITY, MISSING_HEADERS, 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
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>
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:
> First, thanks for digging further into this.
> 
> I'm guessing that I am missing some of the developer pieces that
> assisted you in deducing from

No problem.  I was curious about the possible Win 11 Preview connection and 
happened to have a bit of free time to investigate.  Installing the 
ncurses-debuginfo package gave me debugging symbols for use with gdb.  Calculating 
<exception-address> minus <dll-load-address> from your strace gave me the offset 
into the ncurses DLL of the exception on your system.  Then on my own system I 
have a different <dll-load-address> but adding the offset gives me the 
corresponding <exception-address> on my own system.  The rest was using gdb.

[...]
>>> 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 :-/.

I didn't consider that your original libncursesw-10.dll might have been damaged. 
I was kinda fixated on the possibility of Win 11 Preview brokenness ;-).

>> Here's the gdb session from my own Windows 10 machine...
> ... thank you for looking at this in gdb
>>
>> That is all the help/damage I can do at this point.
>> Cheers,
>>
>> ..mark
> 
> I started setup today and observed that the only "pending" actions
> were a bunch of ncurses installs.
> I clicked ok ( and enabled source just in case :-)  ) and watched the
> action begin.
> 
> Uninstall libncurses-devel 6.0-11.20170617 (automatically added)
> Uninstall libncursesw10 6.0-11.20170617 (automatically added)
> Uninstall ncurses 6.0-11.20170617 (automatically added)
> Install libncurses++w10 6.1-1.20190727
> Install libncurses++w10-src 6.1-1.20190727 (source)
> Install libncurses-devel 6.1-1.20190727
> Install libncurses-devel-src 6.1-1.20190727 (source)
> Install libncursesw10 6.1-1.20190727
> Install libncursesw10-src 6.1-1.20190727 (source)
> Install ncurses 6.1-1.20190727
> Install ncurses-src 6.1-1.20190727 (source)
> 
> both bash and more worked
>   ( e.g. bash starts and more doesn't stack dump in this simple case
> 
> 
> c:\cygwin64>cd bin
> c:\cygwin64\bin>path c:\cygwin64\bin;%PATH%
> c:\cygwin64\bin>which which
> /usr/bin/which
> 
> c:\cygwin64\bin>more < NUL
> 
> c:\cygwin64\bin>
> 
> looking back at the downgrade log I see
> 
> Uninstall libncursesw10 6.1-1.20190727 (automatically added)
> Uninstall ncurses 6.1-1.20190727 (automatically added)
> 
> so I think that  I just upgraded to what I had before, not sure if
> something was corrupted before.

That's right, you're back to the version you started with but things are working 
now.  I'm now inclined to think your original ncurses DLL was damaged somehow.  I 
don't know how deeply 'cygcheck -c' checks a package.. It can tell when individual 
files are missing from the package but I don't know if it checksums the files, for 
instance, to discover individual file damage.

I don't think there's anything more to do here but run your working system :-).
Cheers,

..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

- Raw text -