From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>, Jim Porter <jporterbugs@gmail.com>
Cc: 66186@debbugs.gnu.org, jschmidt4gnu@vodafonemail.de
Subject: bug#66186: "make lisp/eshell/esh-proc-tests" fails intermittently since 7e50861ca7ed3f620fe62ac6572f6e88b3600ece
Date: Mon, 25 Sep 2023 00:18:02 -0700 [thread overview]
Message-ID: <2625a345-7888-fd0b-2f69-7ca46770a059@cs.ucla.edu> (raw)
In-Reply-To: <83cyy63g1d.fsf@gnu.org>
On 2023-09-24 23:47, Eli Zaretskii wrote:
> Perhaps process-send-string should install a temporary SIGPIPE
> handler, at least optionally? Paul, WDYT?
Sounds like a recipe for bad race conditions.
I'm not following the problem closely. However, the usual way to handle
this is to use sendto's MSG_NOSIGNAL option (GNU/Linux) or use
setsockopt with SO_NOSIGPIPE (the BSDs and macOS). This should prevent
those SIGPIPEs from occurring.
Alternatively, but this would be a bigger lift, you can arrange for a
SIGPIPE signal handler to be enabled all the time, even in batch mode.
But then you'll need to resurrect the batch-mode code that used to deal
with this sort of thing (and I've forgotten what it is and as I vaguely
recall it was a bit buggy but you can look at the change history). The
basic idea is that in batch mode, if you ignore SIGPIPE then Emacs
should always check for write errors and exit whenever they happen.
next prev parent reply other threads:[~2023-09-25 7:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-24 21:35 bug#66186: "make lisp/eshell/esh-proc-tests" fails intermittently since 7e50861ca7ed3f620fe62ac6572f6e88b3600ece Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-24 23:02 ` Jim Porter
2023-09-25 4:52 ` Eli Zaretskii
2023-09-25 5:34 ` Jim Porter
2023-09-25 5:47 ` Jim Porter
2023-09-25 6:47 ` Eli Zaretskii
2023-09-25 7:18 ` Paul Eggert [this message]
2023-09-25 7:43 ` Eli Zaretskii
2023-09-25 19:12 ` Jim Porter
2023-09-28 20:33 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-01 20:13 ` Jim Porter
2023-09-25 9:01 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2625a345-7888-fd0b-2f69-7ca46770a059@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=66186@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jporterbugs@gmail.com \
--cc=jschmidt4gnu@vodafonemail.de \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).