From: Juri Linkov <juri@linkov.net>
To: 33252@debbugs.gnu.org
Subject: bug#33252: 27.0.50; Recursive password prompt takes over
Date: Sun, 04 Nov 2018 01:41:41 +0200 [thread overview]
Message-ID: <87k1ltafuy.fsf@mail.linkov.net> (raw)
A bug in a shell script caused an infinitive stream of the same output lines:
Password: sh: 1: read: Illegal option -s
Password: sh: 1: read: Illegal option -s
Password: sh: 1: read: Illegal option -s
Password: sh: 1: read: Illegal option -s
Password: sh: 1: read: Illegal option -s
...
Currently Emacs handles such shell output very poorly and fails
with the following backtrace:
Debugger entered--Lisp error: (error "Variable binding depth exceeds max-specpdl-size")
read-string("(In buffer *shell*) Password: sh: 1: read: Ill..." nil t nil)
read-passwd("(In buffer *shell*) Password: sh: 1: read: Ill...")
comint-send-invisible("Password: sh: 1: read: Illegal option -s\nPassword:...")
comint-watch-for-password-prompt("Password: sh: 1: read: Illegal option -s\n\nPassword...")
run-hook-with-args(comint-watch-for-password-prompt "Password: sh: 1: read: Illegal option -s\n\nPassword...")
comint-output-filter(#<process shell<1>> "Password: sh: 1: read: Illegal option -s\n\nPassword...")
...
read-string("(In buffer *shell*) sh: 1: read: Illegal optio..." nil t nil)
read-passwd("(In buffer *shell*) sh: 1: read: Illegal optio...")
comint-send-invisible("sh: 1: read: Illegal option -s\nPassword: sh: 1: re...")
comint-watch-for-password-prompt("sh: 1: read: Illegal option -s\n\nPassword: sh: 1: r...")
run-hook-with-args(comint-watch-for-password-prompt "sh: 1: read: Illegal option -s\n\nPassword: sh: 1: r...")
comint-output-filter(#<process shell<1>> "sh: 1: read: Illegal option -s\n\nPassword: sh: 1: r...")
...
read-string("(In buffer *shell*) sh: 1: read: Illegal optio..." nil t nil)
read-passwd("(In buffer *shell*) sh: 1: read: Illegal optio...")
comint-send-invisible("sh: 1: read: Illegal option -s\nPassword: sh: 1: re...")
comint-watch-for-password-prompt("sh: 1: read: Illegal option -s\n\nPassword: sh: 1: r...")
run-hook-with-args(comint-watch-for-password-prompt "sh: 1: read: Illegal option -s\n\nPassword: sh: 1: r...")
comint-output-filter(#<process shell<1>> "sh: 1: read: Illegal option -s\n\nPassword: sh: 1: r...")
...
A reproducible short test case:
0. emacs -Q
1. M-&
while true; do echo -n "Password: "; sleep 1; done
RET
After 42 seconds Emacs session becomes completely unusable, and control
can be regained only after killing the shell script from outside Emacs.
next reply other threads:[~2018-11-03 23:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-03 23:41 Juri Linkov [this message]
2019-07-10 13:24 ` bug#33252: 27.0.50; Recursive password prompt takes over Lars Ingebrigtsen
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=87k1ltafuy.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=33252@debbugs.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).