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: Wed, 10 Nov 2021 17:23:21 +0000 [thread overview]
Message-ID: <f5bfss33oxi.fsf@ecclerig.inf.ed.ac.uk> (raw)
In-Reply-To: <4b937b32-e348-19d2-2406-c55fa12e20a3@cornell.edu> (Ken Brown via Cygwin's message of "Wed\, 10 Nov 2021 09\:47\:31 -0500")
Ken Brown via Cygwin writes:
> On 11/9/2021 9:53 PM, Ken Brown via Cygwin wrote:
>> Back to the drawing board.
>
> It finally occurred to me to stop looking for a bug in
> fhandler_pipe::raw_read and instead see if something is in fact
> repeatedly writing to the pipe, so that drain_signal_event_pipe
> never finishes. Putting a breakpoint at fhandler_pipe::raw_write, I
> found that this is in fact the case. While the main thread is
> repeatedly reading from the pipe, a second thread is repeatedly
> writing to it. Here's the backtrace of that thread:
Argh. Thanks for the hard labour on this. This is not a part of the
XEmacs code I have any experience of. Is there any clue you can give
about how things changed in all the September commits to
fhandler_pipe.cc that might have exposed the XEmacs bug?
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-10 17:23 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
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 [this message]
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=f5bfss33oxi.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).