X-Recipient: archive-cygwin AT delorie DOT com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org ED4E93950E68
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1628572184;
	bh=K277Rfr5nXX/g7XsmDCTtDgQdkRbslFLdx0GMVOP2H4=;
	h=Date:To:Subject:In-Reply-To:References:List-Id:List-Unsubscribe:
	 List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:
	 From;
	b=STQkTH7LJIfQP7gCuTZmjOG6K/UB7Uce5IWVI1D2BAWQepFTVEZ5z1uGondytDv03
	 XyCrF3huxVdqHgHElXCLxSB+aML9jGEjhWh2Kn8frTBQPRFn+orru0NOM6SLj1pbLA
	 E5jCNMKEtjPFqe+uAxwD3aE5Dsr0TdO7cn1fjsPw=
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 351C33950C8B
DKIM-Filter: OpenDKIM Filter v2.10.3 conssluserg-01.nifty.com 17A57lku014036
X-Nifty-SrcIP: [110.4.221.123]
Date: Tue, 10 Aug 2021 14:07:52 +0900
To: cygwin AT cygwin DOT com
Subject: Re: many cygwin shells/tools (tcsh, fish, bash, and zsh) crashing
 STATUS_ACCESS_VIOLATION
Message-Id: <20210810140752.fa6a245a2ba432855929f97f@nifty.ne.jp>
In-Reply-To: <CAJtSMguEyZ=cyVrfigEnBVM1JdRG04sk4A=nxh6+W6w_ZvbuQw@mail.gmail.com>
References: <CAJtSMguEyZ=cyVrfigEnBVM1JdRG04sk4A=nxh6+W6w_ZvbuQw AT mail DOT gmail DOT com>
X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32)
Mime-Version: 1.0
X-Spam-Status: No, score=-3.7 required=5.0 tests=BAYES_00, DKIM_SIGNED,
 DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, KAM_SHORT, NICE_REPLY_A,
 RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2, SPF_HELO_NONE, SPF_PASS,
 TXREP autolearn=ham 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>
From: Takashi Yano via Cygwin <cygwin AT cygwin DOT com>
Reply-To: Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
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>

On Mon, 9 Aug 2021 21:36:15 -0700
David Dyck wrote:
> I'm having trouble getting cygwin bash to start up - I tried older
> versions of bash, and I see that other tools are crashing also.  I'm
> looking for ideas on how to collect the useful information to begin
> the path to getting operation of cygwin restored.
> 
> 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.

> seems like this computer ran cygwin bash probably in May of 2021.
> 
> To test cygwin tools I was able to add my cygwin bin directory to the path
> 
> c:\cygwin64\bin>path c:\cygwin64\bin;%PATH%
> 
> though normally I start cygwin with
>   C:\cygwin64\bin\mintty.exe -i /Cygwin-Terminal.ico -
> 
> 
> c:\cygwin64\bin>tcsh
>       0 [main] -csh 543 cygwin_exception::open_stackdumpfile: Dumping
> stack trace to tcsh.exe.stackdump
> 
> c:\cygwin64\bin>fish
>       0 [main] fish 73 cygwin_exception::open_stackdumpfile: Dumping
> stack trace to fish.exe.stackdump
> 
> c:\cygwin64\bin>bash
>       0 [main] bash 566 cygwin_exception::open_stackdumpfile: Dumping
> stack trace to bash.exe.stackdump
> 
> c:\cygwin64\bin>zsh
>       0 [main] zsh 1146 cygwin_exception::open_stackdumpfile: Dumping
> stack trace to zsh.exe.stackdump
> 
> # some shells start up
> 
> c:\cygwin64\bin>ash
> $ exit
> 
> c:\cygwin64\bin>dash
> $ exit
> 
> # even less crashes
> 
> 
> 
> c:\cygwin64\bin>.\date | less
>       1 [main] less 1907 cygwin_exception::open_stackdumpfile: Dumping
> stack trace to less.exe.stackdump
> 
> ---
> on the other hand, many programs can give their initial help
> 
> c:\cygwin64\bin>bash --version
> GNU bash, version 4.4.12(3)-release (x86_64-unknown-cygwin)
> Copyright (C) 2016 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
> 
> This is free software; you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
> 
> here is a sample stackdump
> 
> $ wc -l *.stackdump
>    25 bash.exe.stackdump
>     9 fish.exe.stackdump
>     9 infocmp.exe.stackdump
>    18 less.exe.stackdump
>     9 more.exe.stackdump
>    28 python2.7.exe.stackdump
>    25 sh.exe.stackdump
>    33 tcsh.exe.stackdump
>    22 zsh.exe.stackdump
>   178 total
> $ dash
> $ date | more
> Segmentation fault (core dumped)
> $ cat more.exe.stackdump
> Exception: STATUS_ACCESS_VIOLATION at rip=003E07E8A37
> rax=00000003EFB1A170 rbx=0000000000000001 rcx=000000018037C76D
> rdx=0000000000000001 rsi=000000018037C76D rdi=00000000FFFFC514
> r8 =00000000FFFFC514 r9 =0000000000000000 r10=000000000000004D
> r11=00000001004053BE r12=0000000000000000 r13=00000000FFFFCDF0
> r14=0000000000000000 r15=0000000000000000
> rbp=0000000000000001 rsp=00000000FFFFC448
> program=C:\cygwin64\bin\more.exe, pid 145, thread main
> cs=0033 ds=002B es=002B fs=0053 gs=002B ss=002B


-- 
Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>

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