all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Chris Hunt <chrahunt@gmail.com>
Cc: 44642@debbugs.gnu.org
Subject: bug#44642: 27.1; read-string does not signal on EOF after calling server-eval-at
Date: Sat, 14 Nov 2020 20:47:46 +0200	[thread overview]
Message-ID: <83v9e7u65p.fsf@gnu.org> (raw)
In-Reply-To: <CAH+Wm48AXTVFD7r835aA-+ZVu8ZogDWwSgTbP0K4gULNLZsVRw@mail.gmail.com> (message from Chris Hunt on Sat, 14 Nov 2020 11:46:42 -0500)

> From: Chris Hunt <chrahunt@gmail.com>
> Date: Sat, 14 Nov 2020 11:46:42 -0500
> 
> On my machine, this outputs:
> 
> #+begin_src text
> [script] test 1
> Received ’notest’
> Error reading from stdin
> [script] test 1 complete
> [script] test 2
> Received ’test’
> Sending request to server
> Response received from server ’hello from server’
> #+end_src
> 
> and hangs. According to `top', the non-daemon process is consuming
> 100% of a CPU core.
> 
> xbacktrace in gdb of the non-daemon emacs shows
> 
> #+begin_src text
> "read-string" (0xb5783470)
> "eval-buffer" (0xb5783660)
> "load-with-code-conversion" (0xb5783928)
> "load" (0xb5783c18)
> "command-line-1" (0xb5784260)
> "command-line" (0xb5784ac8)
> "normal-top-level" (0xb5784e20)
> #+end_src

Please show also the C-level backtrace from GDB.

Thanks.





  reply	other threads:[~2020-11-14 18:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-14 16:46 bug#44642: 27.1; read-string does not signal on EOF after calling server-eval-at Chris Hunt
2020-11-14 18:47 ` Eli Zaretskii [this message]
2020-11-14 19:42   ` Chris Hunt
2020-11-14 19:58     ` Eli Zaretskii
2020-11-14 20:40       ` Chris Hunt
2020-11-14 20:50         ` Chris Hunt
2020-11-14 21:43       ` Andreas Schwab
2020-11-15  3:25         ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83v9e7u65p.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=44642@debbugs.gnu.org \
    --cc=chrahunt@gmail.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.