From: Allen Li <darkfeline@felesatra.moe>
To: Robert Pluim <rpluim@gmail.com>
Cc: 37786@debbugs.gnu.org
Subject: bug#37786: 26.3; Emacs crashes when calling function to decode string
Date: Fri, 18 Oct 2019 18:18:34 -0700 [thread overview]
Message-ID: <80imol1qj9.fsf@felesatra.moe> (raw)
In-Reply-To: <m2wod2qt7m.fsf@gmail.com> (Robert Pluim's message of "Fri, 18 Oct 2019 11:49:17 +0200")
Robert Pluim <rpluim@gmail.com> writes:
>>>>>> On Thu, 17 Oct 2019 21:28:35 -0700, Allen Li <darkfeline@felesatra.moe> said:
>
> Allen> This is the backtrace using the simpler repro from Robert.
>
> Allen> #0 0x0000000000565ae9 in terminate_due_to_signal (sig=6, backtrace_limit=40) at emacs.c:363
> Allen> #1 0x000000000058ca83 in emacs_abort () at sysdep.c:2380
> Allen> #2 0x000000000045c17e in redisplay_internal () at xdisp.c:13797
> Allen> #3 0x000000000045e0b7 in redisplay_preserve_echo_area (from_where=13) at xdisp.c:14602
> Allen> #4 0x0000000000667fbe in Fdelete_process (process=XIL(0x6aa3395)) at process.c:1054
> Allen> #5 0x000000000067716b in kill_buffer_processes (buffer=XIL(0)) at process.c:7819
> Allen> #6 0x00000000005683d0 in shut_down_emacs (sig=0, stuff=XIL(0)) at emacs.c:2096
> Allen> #7 0x000000000052d854 in x_connection_closed (dpy=0x2b77f50,
> Allen> error_message=0x7fffffff6fc0 "X protocol error: BadLength (poly
> Allen> request too large or internal Xlib length error) on protocol request
> Allen> 139", ioerror=false) at xterm.c:9799
>
> I thought weʼd fixed these kinds of bugs, but obviously not. Can you
> try your test in combination with the following from etc/DEBUG, it
> should tell us which font is responsible:
>
> For X protocol errors related to displaying unusual characters or to
> font-related customizations, try invoking Emacs like this:
>
> XFT_DEBUG=16 emacs -xrm "emacs.synchronous: true"
>
> This should produce information from the libXft library which could
> give useful hints regarding font-related problems in that library.
That gives me the following output:
Loading file /usr/share/fonts/adobe-source-code-pro/SourceCodePro-Regular.otf/0
FontFile /usr/share/fonts/adobe-source-code-pro/SourceCodePro-It.otf/0 matches new
Loading file /usr/share/fonts/adobe-source-code-pro/SourceCodePro-It.otf/0
FontFile /usr/share/fonts/adobe-source-code-pro/SourceCodePro-Light.otf/0 matches new
Loading file /usr/share/fonts/adobe-source-code-pro/SourceCodePro-Light.otf/0
FontFile /usr/share/fonts/adobe-source-code-pro/SourceCodePro-Bold.otf/0 matches new
Loading file /usr/share/fonts/adobe-source-code-pro/SourceCodePro-Bold.otf/0
FontFile /usr/share/fonts/adobe-source-code-pro/SourceCodePro-Regular.otf/0 matches existing (2)
FontFile /usr/share/fonts/adobe-source-code-pro/SourceCodePro-Light.otf/0 matches existing (2)
FontFile /usr/share/fonts/adobe-source-code-pro/SourceCodePro-Bold.otf/0 matches existing (2)
FontFile /usr/share/fonts/adobe-source-code-pro/SourceCodePro-Regular.otf/0 matches existing (3)
FontFile /usr/share/fonts/adobe-source-code-pro/SourceCodePro-Light.otf/0 matches existing (3)
FontFile /usr/share/fonts/adobe-source-code-pro/SourceCodePro-Bold.otf/0 matches existing (3)
FontFile /usr/share/fonts/adobe-source-code-pro/SourceCodePro-Regular.otf/0 matches existing (4)
FontFile /usr/share/fonts/adobe-source-code-pro/SourceCodePro-Regular.otf/0 matches existing (4)
FontFile /usr/share/fonts/noto/NotoColorEmoji.ttf/0 matches new
Loading file /usr/share/fonts/noto/NotoColorEmoji.ttf/0
and then Emacs hangs at this point.
>
> Regards
>
> Robert
next prev parent reply other threads:[~2019-10-19 1:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 4:11 bug#37786: 26.3; Emacs crashes when calling function to decode string Allen Li
2019-10-17 4:22 ` Lars Ingebrigtsen
2019-10-17 9:53 ` Robert Pluim
2019-10-18 4:28 ` Allen Li
2019-10-18 9:49 ` Robert Pluim
2019-10-19 1:18 ` Allen Li [this message]
2019-10-21 10:02 ` Robert Pluim
2019-10-22 3:44 ` Allen Li
2019-10-22 8:18 ` Robert Pluim
2019-10-23 3:25 ` Allen Li
2019-10-25 16:32 ` Robert Pluim
2019-10-26 9:44 ` Allen Li
2019-10-27 8:26 ` Robert Pluim
2019-11-05 17:40 ` Robert Pluim
2019-11-13 14:03 ` Robert Pluim
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=80imol1qj9.fsf@felesatra.moe \
--to=darkfeline@felesatra.moe \
--cc=37786@debbugs.gnu.org \
--cc=rpluim@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 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).