From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: Another pipe-related problem?
Date: Mon, 8 Nov 2021 13:52:58 -0500 [thread overview]
Message-ID: <258eb4f9-101d-e953-816d-ca258ee88989@cornell.edu> (raw)
In-Reply-To: <05c4180e-396b-4af3-ac0c-2ab8125df17e@cornell.edu>
On 11/8/2021 9:35 AM, Ken Brown via Cygwin wrote:
> On 11/8/2021 8:12 AM, Henry S. Thompson via Cygwin wrote:
>> 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.
>
> This backtrace doesn't match the source of Cygwin's XEmacs package (which exists
> on 32-bit Cygwin only), so I assume you built this yourself, using a different
> version of XEmacs. Cygwin's XEmacs doesn't hang for me.
>
> Please provide build instructions for the version you compiled. Your backtrace
> shows that fhandler_pipe::raw_read is blocked waiting for a mutex
Alternatively, XEmacs might be in an infinite loop starting at frame 8 or 9,
repeatedly trying to read and failing because it can't get the mutex. Either
way, we need the sources in order to go further.
Ken
next prev parent reply other threads:[~2021-11-08 18:53 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 [this message]
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=258eb4f9-101d-e953-816d-ca258ee88989@cornell.edu \
--to=kbrown@cornell.edu \
--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).