From: Eli Zaretskii <eliz@gnu.org>
To: Aaron Jensen <aaronjensen@gmail.com>
Cc: 30852@debbugs.gnu.org
Subject: bug#30852: 27.0.50; infinite loop in internal-get-lisp-face-attribute
Date: Mon, 19 Mar 2018 08:54:49 +0200 [thread overview]
Message-ID: <83sh8wo8qu.fsf@gnu.org> (raw)
In-Reply-To: <m2a7v4d98u.fsf@gmail.com> (message from Aaron Jensen on Sun, 18 Mar 2018 20:39:29 -0700)
> From: Aaron Jensen <aaronjensen@gmail.com>
> Date: Sun, 18 Mar 2018 20:39:29 -0700
>
> This could be a bug in a package: eterm-256color but I wanted to report
> it in case it's an emacs bug.
>
> 0. Install https://github.com/dieggsy/eterm-256color devel branch
> 1. emacs -Q
> 2. (require 'eterm-256color-mode)
> 3. (add-hook 'term-mode-hook #'eterm-256color-mode)
> 4. M-x ansi-term
>
> It's possible that you'll need a color prompt to trigger the inf loop,
> I'm not sure.
>
> Here is the trace of where it is stuck:
>
> internal-get-lisp-face-attribute
Are you that saying eterm-256color causes Emacs to create a face alist
that is a circular list?
> * thread #1, queue = 'com.apple.main-thread', stop reason = signal SIGSTOP
> * frame #0: 0x00000001002a29bd emacs`assq_no_quit(key=0x000000000204ed50, list=0x00000001152f10f3) at fns.c:1422
> frame #1: 0x000000010016a4d3 emacs`lface_from_face_name_no_resolve(f=0x0000000105008bb0, face_name=0x000000000204ed50, signal_p=true) at xfaces.c:1859
Can you show the value of f->face_alist in this frame #1?
next prev parent reply other threads:[~2018-03-19 6:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 3:39 bug#30852: 27.0.50; infinite loop in internal-get-lisp-face-attribute Aaron Jensen
2018-03-19 3:50 ` bug#30852: (27.0.50; infinite loop in internal-get-lisp-face-attribute) Aaron Jensen
2018-03-19 4:59 ` Aaron Jensen
2018-03-19 6:54 ` Eli Zaretskii [this message]
2018-03-19 14:56 ` bug#30852: 27.0.50; infinite loop in internal-get-lisp-face-attribute Aaron Jensen
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=83sh8wo8qu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=30852@debbugs.gnu.org \
--cc=aaronjensen@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.