From: "Henry S. Thompson" <ht@inf.ed.ac.uk>
To: Ken Brown via Cygwin <cygwin@cygwin.com>
Subject: Another pipe-related problem?
Date: Mon, 08 Nov 2021 13:12:10 +0000 [thread overview]
Message-ID: <f5br1bqaj11.fsf@ecclerig.inf.ed.ac.uk> (raw)
Running on Windows-10 21H1
With Cygwin 3.3.0 and 3.3.1 I get a hang every time I try to launch XEmacs:
#0 0x00007ffdf31cd474 in ntdll!ZwQueryTimer ()
from /c/Windows/SYSTEM32/ntdll.dll
#1 0x00000001800479fa in cygwait (object=<optimized out>, timeout=0xffff09a0,
timeout@entry=0x0, mask=mask@entry=5)
at /usr/x86_64-pc-cygwin/sys-root/usr/include/w32api/psdk_inc/intrin-impl.h:838
#2 0x000000018008f716 in cygwait (mask=<optimized out>,
howlong=<optimized out>, h=<optimized out>)
at /usr/src/debug/cygwin-3.3.1-1/winsup/cygwin/cygwait.h:45
#3 cygwait (howlong=<optimized out>, h=<optimized out>)
at /usr/src/debug/cygwin-3.3.1-1/winsup/cygwin/cygwait.h:51
#4 fhandler_pipe::raw_read (this=0x18034fe80, ptr=0xffff0bc0,
len=@0xffff0b40: 128)
at /usr/src/debug/cygwin-3.3.1-1/winsup/cygwin/fhandler_pipe.cc:296
#5 0x0000000180069244 in fhandler_base::read (this=0x18034fe80,
in_ptr=0xffff0bc0, len=@0xffff0b40: 128)
at /usr/src/debug/cygwin-3.3.1-1/winsup/cygwin/fhandler.cc:819
#6 0x000000018013ffcc in read (fd=3, ptr=0xffff0bc0, len=<optimized out>)
at /usr/src/debug/cygwin-3.3.1-1/winsup/cygwin/dtable.h:64
#7 0x000000018018e88b in _sigfe () at sigfe.s:35
#8 0x000000010066a11d in retry_read_1 (fildes=3, buf=0xffff0bc0, nbyte=128,
allow_quit=0) at sysdep.c:2425
#9 0x000000010066a171 in retry_read (fildes=3, buf=0xffff0bc0, nbyte=128)
at sysdep.c:2437
#10 0x0000000100494d86 in drain_signal_event_pipe () at event-unixoid.c:159
#11 0x000000010056d1dc in mswindows_need_event (badly_p=1) at event-msw.c:1432
This is an old executable, has worked since 2015 (!), but recompiling
didn't help. Reverting to 3.2 lets it run again.
I can try to debug further if instructed in how to do so, but
constructing a simple test case is beyond me...
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 reply other threads:[~2021-11-08 13:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-08 13:12 Henry S. Thompson [this message]
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
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=f5br1bqaj11.fsf@ecclerig.inf.ed.ac.uk \
--to=ht@inf.ed.ac.uk \
--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).