unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: phst@google.com, rgm@gnu.org, emacs-devel@gnu.org
Subject: Re: master 64f2c96 2/2: Make a process test faster.
Date: Sun, 10 Jan 2021 18:39:30 +0200	[thread overview]
Message-ID: <83bldwhhkt.fsf@gnu.org> (raw)
In-Reply-To: <CAArVCkQDj6_dJ6PdK95VAT5R_t-5H3wVTKxEPKPKygmrPkHWRw@mail.gmail.com> (message from Philipp Stephani on Sat, 9 Jan 2021 22:00:45 +0100)

> From: Philipp Stephani <p.stephani2@gmail.com>
> Date: Sat, 9 Jan 2021 22:00:45 +0100
> Cc: Philipp Stephani <phst@google.com>, Emacs developers <emacs-devel@gnu.org>
> 2. The other one happens if SIGCHLD is signaled during
> wait_reading_process_output. Then wait_reading_process_output will
> wait forever, since the stdout FD never gets closed and it doesn't see
> the process status update in time.

Do you mean that wait_reading_process_output has this problem in
general, or just in this particular scenario?  If the former, I'm
surprised, as we are using this code for a very long time.  If the
latter, can you elaborate on the situation, and what does SIGCHLD have
to do with closing stdout?



  reply	other threads:[~2021-01-10 16:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210102125533.3832.43853@vcs0.savannah.gnu.org>
     [not found] ` <20210102125536.C3FED2094D@vcs0.savannah.gnu.org>
2021-01-03 17:41   ` master 64f2c96 2/2: Make a process test faster Glenn Morris
2021-01-04 21:24     ` Philipp Stephani
2021-01-05 14:27       ` Philipp Stephani
2021-01-08  1:38         ` Glenn Morris
2021-01-08  9:01           ` Michael Albinus
2021-01-09 18:12           ` Philipp Stephani
2021-01-09 21:00             ` Philipp Stephani
2021-01-10 16:39               ` Eli Zaretskii [this message]
2021-01-10 17:17                 ` Philipp Stephani
2021-01-16 19:19                   ` Philipp Stephani

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=83bldwhhkt.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=p.stephani2@gmail.com \
    --cc=phst@google.com \
    --cc=rgm@gnu.org \
    /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).