From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: raise(-1) has stopped returning an error recently
Date: Mon, 29 Nov 2021 11:41:28 +0100 [thread overview]
Message-ID: <YaSuWCmddGGgk8KB@calimero.vinschen.de> (raw)
In-Reply-To: <YaFxOPt5VbPxqhmx@slk1.local.net>
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
prev parent reply other threads:[~2021-11-29 10:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 5:20 Duncan Roe
2021-11-22 10:25 ` Corinna Vinschen
2021-11-22 13:06 ` Corinna Vinschen
2021-11-23 8:27 ` Duncan Roe
2021-11-23 9:50 ` Corinna Vinschen
2021-11-23 18:18 ` Brian Inglis
2021-11-23 22:36 ` Duncan Roe
2021-11-24 9:25 ` Corinna Vinschen
2021-11-24 18:01 ` Brian Inglis
2021-11-25 12:54 ` Corinna Vinschen
2021-11-27 7:24 ` Brian Inglis
2021-11-28 3:04 ` Duncan Roe
2021-11-26 23:43 ` Duncan Roe
2021-11-29 10:41 ` Corinna Vinschen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YaSuWCmddGGgk8KB@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).