unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Rajeev N via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: larsi@gnus.org, 49682@debbugs.gnu.org, dgutov@yandex.ru
Subject: bug#49682: 27.2.50; accept-process-output within accept-process-output hangs emacs
Date: Tue, 27 Jul 2021 17:40:27 -0400	[thread overview]
Message-ID: <875ywvzb90.fsf@hm.sivalik.com> (raw)
In-Reply-To: <831r7jvewf.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 27 Jul 2021 20:35:12 +0300")

It seems to be a bug-  a similar bug was fixed recently.

  http://git.savannah.gnu.org/cgit/emacs.git/commit/src/process.c?id=1773679af3241919a85d6174b1554070a63cca79

On Tue, 27 Jul 2021 at  8:35 PM +0300, Eli Zaretskii wrote:

#+begin_quote
> Disposition-Notification-To: rajeev.jnk@sivalik.com
> From: Rajeev N <rajeev.jnk@sivalik.com>
> Cc: Lars Ingebrigtsen <larsi@gnus.org>,  49682@debbugs.gnu.org,  Eli
>  Zaretskii <eliz@gnu.org>
> Date: Tue, 27 Jul 2021 13:22:54 -0400
> 
> Another input that may help resolve the issue:
> 
> In the pselect loop- file descriptor 19 is show in CLOSE_WAIT state by lsof.
> 
> lsof:
> 
> emacs   66152 rajeev   19u     IPv4            2567759      0t0      TCP hp:37994->wildebeest.gnu.org:https (CLOSE_WAIT)

 If the remote host closed the connection, why isn't our sentinel being
 called and the connection closed?
#+end_quote





  reply	other threads:[~2021-07-27 21:40 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-21 14:58 bug#49682: 27.2.50; accept-process-output within accept-process-output hangs emacs Rajeev N via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-07-21 15:14 ` Lars Ingebrigtsen
2021-07-21 16:14   ` Rajeev N via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-07-21 16:18     ` Lars Ingebrigtsen
     [not found]       ` <87tukntz2m.fsf@hm.sivalik.com>
2021-07-21 16:40         ` Lars Ingebrigtsen
2021-07-23 17:00       ` Rajeev N via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-07-24 10:28         ` Lars Ingebrigtsen
2021-07-24 10:46           ` Rajeev N via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-07-26 18:58         ` Dmitry Gutov
2021-07-26 19:54           ` Rajeev N via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-07-26 20:22             ` Dmitry Gutov
2021-07-26 20:55               ` Rajeev N via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-07-27 14:13                 ` Dmitry Gutov
2021-07-27 17:22                   ` Rajeev N via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-07-27 17:35                     ` Eli Zaretskii
2021-07-27 21:40                       ` Rajeev N via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-07-28 16:12                         ` Eli Zaretskii
2021-07-28 17:12                           ` Rajeev N via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-08-06 16:55                           ` Robert Pluim
2021-07-21 19:29 ` Eli Zaretskii
2021-07-21 21:32   ` Lars Ingebrigtsen
2021-07-21 21:53     ` Rajeev N via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-07-22  5:47     ` Eli Zaretskii
2021-07-23 18:30       ` Dmitry Gutov
2023-11-06 17:14 ` LdBeth
2023-11-06 17:39   ` Eli Zaretskii
2023-11-06 20:27     ` LdBeth
2023-11-07  9:24       ` Michael Albinus
2023-11-08 15:50     ` Kazuhiro Ito
2023-11-08 16:37       ` Eli Zaretskii

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=875ywvzb90.fsf@hm.sivalik.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=49682@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=eliz@gnu.org \
    --cc=larsi@gnus.org \
    --cc=rajeev.jnk@sivalik.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.
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).