X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 82D773835C11 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1638182523; bh=rXTfq18lLhz3n6J1XXNaO5KpjrCpbwyvC+DDc9hK4co=; h=Date:To:Subject:References:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=vqnYYbUGkDuzlqgrpM/ozgFOoy+i1oW1vKz8uTOnETcs8IX8vpkb5bRe4kbrKaz9M j67coeW8r22AH83RI28JfmnGTfLRRiDkXZHm2ucjPiF67bPBeMKr6PXR0VHVydBO9I uhpPIBBECShLl2g0VK2h/9qOVoBwC3iyuMRSPvNk= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org C348B385841B Date: Mon, 29 Nov 2021 11:41:28 +0100 To: cygwin AT cygwin DOT com Subject: Re: raise(-1) has stopped returning an error recently Message-ID: Mail-Followup-To: cygwin AT cygwin DOT com References: <42c9bb90-dd78-edfa-99ff-f65f7e000956 AT SystematicSw DOT ab DOT ca> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-Provags-ID: V03:K1:CE3IcMpsWfAe+fmrndBczSnOt68rP3I436fi3fRCy5mVkxOCERZ eeFMk7FP2fa6WvBdkkeoE0mz7iqinJ4KzY70aDWJkQ9e24chhiKRqXbqxhlE9TvkDodcB2i BV3fsPx2E342y1FV9g1g8+SkcUkcRoQ1AjBuk73feEZRu8nqjHSZlRscQNVOMeadO7fl60N VUT48Tsc5LND4LBt76y9g== X-UI-Out-Filterresults: notjunk:1;V03:K0:Zq+BKmgXM+I=:XgNg7c7s7qAhVigbVOHdKG VAn6yzrMDqmJYWwI5NisTdu4AmVC0TkwTSsBjOir0BQbWUOUK9HhIMI+VLchrZYqeaAJuJvwo ACynTRRfde524w5LB4vbuOrzmQIUAmMSjK3Wq9pLnPasf5/xmeI54v0kklOdqq/xwG37D3ymZ xPgJnj40VRWrmkIMC2IVeA9X2Sl1/I07npTWomLatRpSJFJUkZ7YB4KdZDhTxV8ciwekwIAPg LO2Wns7z8z6yn00TeYCst9OTj+CXLKktLzXPwEd7mqRYarWwcT7suWh21U73wIVr9aArn6NIE fJDHGFsSklahNZwzUsjMRIwL4oURX35PS6JQ4Xf+8YRmlnbg7L97GIzGYgB77bjqXfi99kqkZ +bcYZEuZIKhqdl1l638toQOAkZo2ctdrHb9Mb8eF2hue8bCByMNSKEz/5l2eAIye6xAdP0rsb sYrHR/VxnUVIQ22B1/ofmWefI8bMqx9Q+brHi7uHABydCH7y2OyOCNTKMlpk7UZkZ00GMsYA9 wOU3rXujrneMUSnN0bEiCAQgKUIrN/vpUjOB/79qy6VKZm1nGhV9H0yxRAvEJtLuVh/vToUq8 CjeTfAWR9RY69RZsPxn+dLlRRlBmLw+biydPOmFKB9N/8wSZxnTdxS+DKi5h5NW61aIIFHMVY oxKJJmxh0KdDvYF2L+04Z55QFATxsDX6ugfYHk65lNdDqFfV/v+zddyQEhGMkfNGSCZs2SJF9 qy52VjRE2+VJlPgf X-Spam-Status: No, score=-99.4 required=5.0 tests=BAYES_00, GOOD_FROM_CORINNA_CYGWIN, KAM_DMARC_NONE, KAM_DMARC_STATUS, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2, SPF_HELO_NONE, SPF_NEUTRAL, 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Corinna Vinschen via Cygwin Reply-To: cygwin AT cygwin DOT com Cc: Corinna Vinschen 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" On Nov 27 10:43, Duncan Roe wrote: > On Wed, Nov 24, 2021 at 10:25:46AM +0100, cygwin wrote: [...] > > > > What is that "permanent restriction" in Cygwin? Is that something we > > could fix or something unfixable? Did you try to debug Cygwin in terms > > of that problem? If not, could you extract a reduced, very simple > > stand-alone testcase for further debugging? > > > The restriction is in grep/gnulib source. From > https://debbugs.gnu.org/cgi/bugreport.cgi?bug=27555#5 > > >> I've determined the cause, at least. The sole caller of mbstoupper > >> (which contained the relevant __CYGWIN__-specific > >> surrogate-pair-handling code) was removed by the improvements of > >> v2.21-63-g8a33cde, and not long after, I noticed that mbstoupper was > >> no longer used, so removed it altogether. > > I submitted a patch to save anyone else wasting time over this. So please don't > you, Great, thanks! Corinna -- 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