From: Katsumi Yamaoka <yamaoka@jpl.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 23158 <23158@debbugs.gnu.org>
Subject: bug#23158: 25.1.50; crash by consecutive http accesses
Date: Thu, 31 Mar 2016 11:31:52 +0900 [thread overview]
Message-ID: <b4mr3erqsx3.fsf@jpl.org> (raw)
In-Reply-To: <b4m60w48p2e.fsf@jpl.org>
On Wed, 30 Mar 2016 18:23:19 +0300, Eli Zaretskii wrote:
>> those consecutive http accesses seem to crash Emacs.
> Thanks. Can you try reproducing the problem in an unoptimized build,
> and show the backtrace from that?
I built Emacs from the git master with the option CFLAGS='-O0'
and verified it works for the test code with no problem. However,
for reading the spam mail in question, Emacs doesn't crash but it
gets to be unusable; when I try to run some command, Emacs says
Wrong type argument: sequencep, #<process www.gravatar.com<46>>
and does not proceed. A Lisp backtrace follows:
Debugger entered--Lisp error: (wrong-type-argument sequencep #<process www.gravatar.com<46>>)
process-list()
window--process-window-list()
window--adjust-process-windows()
read-from-minibuffer("Switch to buffer in other frame (default *Summary nnml:tmp*): " nil (keymap (10 . minibuffer-complete-and-exit) (13 . minibuffer-complete-and-exit) keymap (menu-bar keymap (minibuf "Minibuf" keymap (tab menu-item "Complete" minibuffer-complete :help "Complete as far as possible") (space menu-item "Complete Word" minibuffer-complete-word :help "Complete at most one word") (63 menu-item "List Completions" minibuffer-completion-help :help "Display all possible completions") "Minibuf")) (27 keymap (118 . switch-to-completions)) (prior . switch-to-completions) (63 . minibuffer-completion-help) (32 . minibuffer-complete-word) (9 . minibuffer-complete) keymap (menu-bar keymap (minibuf "Minibuf" keymap (previous menu-item "Previous History Item" previous-history-element :help "Put previous minibuffer history element in the minibuffer") (next menu-item "Next History Item" next-history-element :help "Put next minibuffer history element in the minibuffer") (isearch-backward menu-item "Isearch History Backward" isearch-backward :help "Incrementally search minibuffer history backward") (isearch-forward menu-item "Isearch History Forward" isearch-forward :help "Incrementally search minibuffer history forward") (return menu-item "Enter" exit-minibuffer :key-sequence "" :help "Terminate input and exit minibuffer") (quit menu-item "Quit" abort-recursive-edit :help "Abort input and exit minibuffer") "Minibuf")) (10 . exit-minibuffer) (13 . exit-minibuffer) (7 . abort-recursive-edit) (C-tab . file-cache-minibuffer-complete) (9 . self-insert-command) (XF86Back . previous-history-element) (up . previous-line-or-history-element) (prior . previous-history-element) (XF86Forward . next-history-element) (down . next-line-or-history-element) (next . next-history-element) (27 keymap (114 . previous-matching-history-element) (115 . next-matching-history-element) (112 . previous-history-element) (110 . next-history-element))) nil buffer-name-history "*Summary nnml:tmp*" nil)
completing-read-default("Switch to buffer in other frame (default *Summary nnml:tmp*): " internal-complete-buffer nil confirm-after-completion nil buffer-name-history "*Summary nnml:tmp*" nil)
read-buffer("Switch to buffer in other frame: " #<buffer *Summary nnml:tmp*> confirm-after-completion)
read-buffer-to-switch("Switch to buffer in other frame: ")
(list (read-buffer-to-switch "Switch to buffer in other frame: "))
call-interactively(switch-to-buffer-other-frame nil nil)
command-execute(switch-to-buffer-other-frame)
Thanks.
next prev parent reply other threads:[~2016-03-31 2:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 6:20 bug#23158: 25.1.50; crash by consecutive http accesses Katsumi Yamaoka
2016-03-30 15:23 ` Eli Zaretskii
2016-03-31 2:31 ` Katsumi Yamaoka [this message]
2016-03-31 2:45 ` Katsumi Yamaoka
2016-03-31 16:33 ` Eli Zaretskii
2016-04-01 0:28 ` Katsumi Yamaoka
2016-04-01 6:51 ` Andreas Schwab
2016-03-30 15:43 ` Lars Magne Ingebrigtsen
2019-09-24 8:16 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b4mr3erqsx3.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=23158@debbugs.gnu.org \
--cc=eliz@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 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.