From: Juri Linkov <juri@linkov.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 52947@debbugs.gnu.org, dlacewell@gmail.com
Subject: bug#52947: 29.0.50; Newline in tab-bar-format causes lockup
Date: Sun, 02 Jan 2022 20:38:31 +0200 [thread overview]
Message-ID: <867dbi56fs.fsf@mail.linkov.net> (raw)
In-Reply-To: <83y23yc7wb.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 02 Jan 2022 20:25:08 +0200")
> Do we want to support newlines there? what would be the purpose of
> having newlines in the tabs?
I don't know, menus can't have newlines too.
> Also, you say "display engine", so does it mean you've found where we
> infloop with these recipes? If so, can you tell the details?
It gives such backtrace:
(gdb) bt
#0 make_lisp_symbol (sym=0x555555cfd9c0 <lispsym>) at lisp.h:1002
#1 0x00005555555b9766 in builtin_lisp_symbol (index=0) at lisp.h:1008
#2 0x00005555555b9cf6 in CHAR_TABLE_REF_ASCII (ct=XIL(0x7ffff0b438dd), idx=10) at lisp.h:2031
#3 0x00005555555b9d3e in CHAR_TABLE_REF (ct=XIL(0x7ffff0b438dd), idx=10) at lisp.h:2042
#4 0x00005555555d16de in lookup_glyphless_char_display (c=10, it=0x7fffffff75d0) at xdisp.c:7410
#5 0x00005555555d1f8c in get_next_display_element (it=0x7fffffff75d0) at xdisp.c:7599
#6 0x00005555555e3133 in display_tab_bar_line (it=0x7fffffff75d0, height=-1) at xdisp.c:13389
#7 0x00005555555e3901 in tab_bar_height (f=0x5555560a2dc8, n_rows=0x5555560a2f08, pixelwise=true) at xdisp.c:13515
#8 0x00005555555e3c27 in redisplay_tab_bar (f=0x5555560a2dc8) at xdisp.c:13597
next prev parent reply other threads:[~2022-01-02 18:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-02 10:17 bug#52947: 29.0.50; Newline in tab-bar-format causes lockup Dustin Lacewell
2022-01-02 17:47 ` Juri Linkov
2022-01-02 18:25 ` Eli Zaretskii
2022-01-02 18:38 ` Juri Linkov [this message]
2022-01-02 19:38 ` Eli Zaretskii
2022-01-04 7:57 ` Juri Linkov
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=867dbi56fs.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=52947@debbugs.gnu.org \
--cc=dlacewell@gmail.com \
--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 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).