From: "Henry S. Thompson" <ht@inf.ed.ac.uk>
To: Ken Brown <kbrown@cornell.edu>
Cc: <cygwin@cygwin.com>
Subject: Re: Another pipe-related problem?
Date: Tue, 09 Nov 2021 14:47:26 +0000 [thread overview]
Message-ID: <f5b1r3p8jy9.fsf@ecclerig.inf.ed.ac.uk> (raw)
In-Reply-To: <eb8d7d4f-d1ed-6f30-2ac3-1b24166243d9@cornell.edu> (Ken Brown's message of "Tue\, 9 Nov 2021 09\:11\:28 -0500")
[private reply -- it's not exactly a private repo, but it's really not
ready for prime-time with users expecting to be able to raise issues
etc.]
Ken Brown writes:
> ...
> I was aware that the bitbucket repo didn't exist, because I tried to get the
> sources there. But I didn't know about the fork. Please point me to it, or
> just make a tarball available to me somehow.
https://foss.heptapod.net/xemacs
>> ...
> I'll have to reproduce the hang myself in order to test this (or
> maybe you could test it), but I now have a new guess: If the read
> call above keeps failing with EINTR, then we're in an infinite loop.
> This could happen because of the following code in
> fhandler_pipe::raw_read:
>
> DWORD waitret = cygwait (read_mtx, timeout);
> switch (waitret)
> {
> case WAIT_OBJECT_0:
> break;
> case WAIT_TIMEOUT:
> set_errno (EAGAIN);
> len = (size_t) -1;
> return;
> default:
> set_errno (EINTR);
> len = (size_t) -1;
> return;
> }
>
Let's wait and see what Takashi says -- I see from github blame that
was introduced between 3.2 and 3.3.0, so certainly _could_ be the
culprit. I've never tried to build my own Cygwin...
Thanks,
ht
--
Henry S. Thompson, School of Informatics, University of Edinburgh
10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
Fax: (44) 131 650-4587, e-mail: ht@inf.ed.ac.uk
URL: http://www.ltg.ed.ac.uk/~ht/
[mail from me _always_ has a .sig like this -- mail without it is forged spam]
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.
next prev parent reply other threads:[~2021-11-09 14:47 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-08 13:12 Henry S. Thompson
2021-11-08 14:35 ` Ken Brown
2021-11-08 18:52 ` Ken Brown
2021-11-09 10:55 ` Henry S. Thompson
2021-11-09 14:11 ` Ken Brown
2021-11-09 14:47 ` Henry S. Thompson [this message]
2021-11-09 22:16 ` Ken Brown
2021-11-09 22:20 ` Ken Brown
2021-11-10 2:53 ` Ken Brown
2021-11-10 3:51 ` Backwoods BC
2021-11-10 14:47 ` Ken Brown
2021-11-10 17:23 ` Henry S. Thompson
2021-11-10 18:03 ` Ken Brown
2021-11-10 18:42 ` Henry S. Thompson
2021-11-10 23:07 ` Andrey Repin
2021-11-11 11:06 ` Andrey Repin
2021-11-11 14:16 ` Ken Brown
2021-12-08 21:09 ` XEmacs versus Cygwin 3.3 (was Re: Another pipe-related problem?) Henry S. Thompson
2021-12-09 8:39 ` Aidan Kehoe
2021-11-09 23:22 ` Another pipe-related problem? Takashi Yano
2021-11-09 23:29 ` Takashi Yano
2021-11-09 23:48 ` Takashi Yano
2021-11-10 0:16 ` Takashi Yano
2021-11-10 0:37 ` Takashi Yano
2021-11-10 2:02 ` Ken Brown
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=f5b1r3p8jy9.fsf@ecclerig.inf.ed.ac.uk \
--to=ht@inf.ed.ac.uk \
--cc=cygwin@cygwin.com \
--cc=kbrown@cornell.edu \
/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).