[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#31214: hang in Faccept_process_output
From: |
Eli Zaretskii |
Subject: |
bug#31214: hang in Faccept_process_output |
Date: |
Fri, 20 Apr 2018 09:28:59 +0300 |
> From: Glenn Morris <rgm@gnu.org>
> Cc: 31214@debbugs.gnu.org
> Date: Thu, 19 Apr 2018 15:48:33 -0400
>
> Eli Zaretskii wrote:
>
> > Then maybe we should pass a non-nil timeout to accept-process-output,
> > and/or a non-nil last argument.
> >
> > IOW, I'm not sure the bug is not in the test itself.
>
> Is it not a standard usage (start a process, and while it's live, accept
> output from it)?
When there are many processes lying around, I wouldn't trust the
defaults to produce the desired effect. Those arguments are there for
a reason, are they not?
> (Could the process by exiting part-way through accept-process-output?)
Which process?
- bug#31214: hang in Faccept_process_output, Glenn Morris, 2018/04/18
- bug#31214: hang in Faccept_process_output, Glenn Morris, 2018/04/19
- bug#31214: hang in Faccept_process_output, Eli Zaretskii, 2018/04/19
- bug#31214: hang in Faccept_process_output, Glenn Morris, 2018/04/19
- bug#31214: hang in Faccept_process_output, Eli Zaretskii, 2018/04/19
- bug#31214: hang in Faccept_process_output, Glenn Morris, 2018/04/19
- bug#31214: hang in Faccept_process_output, Glenn Morris, 2018/04/19
- bug#31214: hang in Faccept_process_output, Eli Zaretskii, 2018/04/20
- bug#31214: hang in Faccept_process_output,
Eli Zaretskii <=
- bug#31214: hang in Faccept_process_output, Glenn Morris, 2018/04/21