X-Recipient:	archive-cygwin AT delorie DOT com
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org 4ABEE3858423
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1637746018;
	bh=Yvp5RWpL1TPxrqvW25evttM9wVffydwB6/smu095API=;
	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=ooSVzuoOMHF6mD5p0HHkMOOQmqpBLJNUsGQdittqmRqnQwKYPoGMFT4iw4+ESQw0r
	H6AdMhByN1CfOxjv8g6Qs0UivHQKqs2nLR91RXtzglOpz5qPjRkAEuLL8KSO4FUflz
	yUyQu+0Z6ZCziVh8OX8Nc9C8NFOmVgWEr5hazN/M=
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.4.1 sourceware.org 948CF385840E
Date:	Wed, 24 Nov 2021 10:25:46 +0100
To:	cygwin AT cygwin DOT com
Subject:	Re: raise(-1) has stopped returning an error recently
Message-ID:	<YZ4FGpEDDar45HC7@calimero.vinschen.de>
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<YZsoj6UvpF6pcbtt AT slk1 DOT local DOT net>
	<YZtwMZ1LUbx+b5+s AT calimero DOT vinschen DOT de>
	<YZuVy5+nbzPtiqdw AT calimero DOT vinschen DOT de>
	<YZyl69ODRcBVnMed AT slk1 DOT local DOT net>
	<YZy5bRsZuulb6FUV AT calimero DOT vinschen DOT de>
	<42c9bb90-dd78-edfa-99ff-f65f7e000956 AT SystematicSw DOT ab DOT ca>
	<YZ1tAfzwlW8C84z4 AT slk1 DOT local DOT net>
MIME-Version:	1.0
In-Reply-To:	<YZ1tAfzwlW8C84z4@slk1.local.net>
X-Provags-ID:	V03:K1:NDtYsoe/PlBhyKiu48Vrs9ce+b1PDwNfFo8OHT74Y2QtYawVowJ
	in3X1hLHPMTWQ9jrx5CN2Bma4JV2jhh1olHHwYUIyzq/iULR08p/RN5x2hM1raIZkizKq5j
	SR5Ieg/cCA1SrHMaq5Uy/avulpcBWqUUiwPAvVgteF5hZxSZOC/2ukaDk+ali0ERFRZg9BO
	ODtmCsSUr9LYWrO9J/1iA==
X-UI-Out-Filterresults:	notjunk:1;V03:K0:Qyz67/vTl40=:iDNRXajxKVxJjxD2lcGLsJ
	8En2uxM+1EHm2wzctTgGHlkbBo6EBH9LGH5kBoPSVv9NtJArHAbfdREnw7MHGKIT5iF9dFeLh
	2FX/TgbL1jjwWX5+nP0x3STVAy+4/mXSluIg1Flbn+Di5wsJChpT1tfpejonWXj2Br0UrXeJl
	TQgSe+PzrwknoztusipIYx8u6pdaVjpDg1Wx9si0rrBZKONr49Qwp8eZxopBpAWY634c99N52
	Nd5md44v+u7w+XeaEGxYdh1FQP1sWiT6jPB59EBOIpFDCQKtAltINR69ST0eZAjTqiSeed/Wr
	+21PNPyFJuk1Jh6ujZL5v9Vh8l9431gxclMOfay/Cuw7w+KSoX27CziuJORRnxKOKXyPRGTYE
	4ON2lJUT5ztoePN4ZjGPPYcrnkE3kood3jGVRgLJa0jh8/56f6HgaFWcmDKt3jAr+UCfqVtA1
	QyNJwU0tmBGSbzto2G8qklA+5d6vJmrLELAgUmuPHMCyEx64dNJvk7f27vvq86jUyBTK0Aa8+
	+il48zULW/1VGmOW/BqGAQvA8w871DtYfHEtARh+BqzFYpkmW8//Z/XUsuW9/jYX5QF0K+JaH
	n2LAUQerrAQZg1qnuIhcmgwt/xVGkxI+SqNZav0aVIq6EYXCEk5yvVPnDQOmly1soP2s4M7ut
	cyIIj0d4CrJkgDEl/vhv7Ii2AEik1jY5D22CG1eMsx3UlxFtxUxKb/dG+UGJtIBl6ltG9Au61
	etOLFt8zgBlMd28o
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
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:	Corinna Vinschen via Cygwin <cygwin AT cygwin DOT com>
Reply-To:	cygwin AT cygwin DOT com
Cc:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
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 Nov 24 09:36, Duncan Roe wrote:
> On Tue, Nov 23, 2021 at 11:18:25AM -0700, Brian Inglis wrote:
> > > On Nov 23 19:27, Duncan Roe wrote:
> > > > Btw to whoever maintains grep for cygwin: 'make check' should pass on
> > > > next release (I patched out the surrogate-pair failre).
> >
> > I had no problems with test-raise last release.
> 
> I don't remember having a problem with it even a few weeks ago.
> 
> > I did with surrogate pairs but after spending too much time on all the test
> > infrastructure around that, decided it was a low probability event, and wait
> > until anyone complains to refer it upstream.
> 
> I wasted time on that too. That's why I patched surrogate-pair to not do its 3rd
> test if 'uname -s' indicates Cygwin.
> 
> For the full story, see https://debbugs.gnu.org/cgi/bugreport.cgi?bug=27555#5

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?

> > Do Cygwin and/or Windows support surrogate pairs in UTF-8?

You mean UTF-16.  UTF-8 doesn't know surrogate pairs, UTF-16 does.
Originally there was UCS-2, 16 bits, with only 65536 code points.
However, Unicode left the BMP already with version 2.0 in 1996, so
UTF-16 and surrogate pairs became necessary.  Windows as well as Cygwin
support them.

> There are 3 tests in surrogate-pair and only the 3rd one failed. So I guess
> surrogate pairs in UTF-8 "mostly work".

UTF-16.  The surrogate stuff is evil at times.  Have a look at the
__utf8_wctomb function in
https://sourceware.org/git/?p=newlib-cygwin.git;a=blob;f=newlib/libc/stdlib/wctomb_r.c
Lone surrogate halfs in an input stream are a problem, for instance.


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

- Raw text -