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 30AFA394C032 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=SystematicSw.ab.ca Authentication-Results: sourceware.org; spf=none smtp.mailfrom=systematicsw.ab.ca X-Authority-Analysis: v=2.4 cv=FMjee8ks c=1 sm=1 tr=0 ts=611208c4 a=T+ovY1NZ+FAi/xYICV7Bgg==:117 a=T+ovY1NZ+FAi/xYICV7Bgg==:17 a=IkcTkHD0fZMA:10 a=94nOnFI1EgyDtX4ev68A:9 a=QEXdDO2ut3YA:10 Subject: Re: many cygwin shells/tools (tcsh, fish, bash, and zsh) crashing STATUS_ACCESS_VIOLATION To: cygwin AT cygwin DOT com References: From: Brian Inglis Organization: Systematic Software Message-ID: <0a68361c-0bca-c2d0-e122-ede519e03e01@SystematicSw.ab.ca> Date: Mon, 9 Aug 2021 23:04:03 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.12.0 MIME-Version: 1.0 In-Reply-To: Content-Language: en-CA X-CMAE-Envelope: MS4xfOCcd/Y7MBZUDgZ10wXwXkI19LzdC4eHiNfgHxjT9MU2NwLRdHMJivVP0jcRMb0K3klieeYGc7QydLloEiilybcEB/UGndqXaHKn0onxsHBk0kgb4saG POmMNh+fG7Ee+8lHr2VMjCSgl6pkGU6gCboMsijRkXgjleGuetVmWWaShRLYPMVDQR+dwFgHdbs81ZtSi/O4QxQyOBecg6NCD2XqSLUhNb/X7uTe51DLEShT X-Spam-Status: No, score=-1160.8 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, NICE_REPLY_A, RCVD_IN_BARRACUDACENTRAL, RCVD_IN_MSPIKE_H4, RCVD_IN_MSPIKE_WL, 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: cygwin AT cygwin DOT com 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" On 2021-08-09 22:36, David Dyck via Cygwin 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] > > seems like this computer ran cygwin bash probably in May of 2021. It's a known problem that after Windows updates, especially Insider, quarterly, or biannually e.g. [20]20H2 [20]2009, it's often advisable to rerun Cygwin Setup and allow packages to be upgraded in case patches are made for new releases, and DLLs be rebased in case address space is occupied by updated Windows components. -- 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.] -- 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