From: Robert Pluim <rpluim@gmail.com>
To: martin rudalics <rudalics@gmx.at>
Cc: emacs-devel@gnu.org
Subject: Re: switching font backends in .emacs.desktop causes crash
Date: Fri, 08 Feb 2019 15:49:38 +0100 [thread overview]
Message-ID: <m28syqnxml.fsf@gmail.com> (raw)
In-Reply-To: <5C5D9032.1060303@gmx.at> (martin rudalics's message of "Fri, 08 Feb 2019 15:20:34 +0100")
martin rudalics <rudalics@gmx.at> writes:
>> Thread 1 "emacs" received signal SIGSEGV, Segmentation fault.
>> 0x00007ffff446468d in XftCharIndex () from /usr/lib/x86_64-linux-gnu/libXft.so.2
>> (gdb) bt
>> #0 0x00007ffff446468d in XftCharIndex () at /usr/lib/x86_64-linux-gnu/libXft.so.2
>> #1 0x0000555555758689 in xftfont_encode_char (font=<optimized out>, c=<optimized out>)
>> at xftfont.c:532
>> #2 0x00005555555d60a9 in get_char_glyph_code (char2b=<synthetic
>> pointer>, font=0x555557b49470, c=<optimized out>) at xdisp.c:25915
>> #3 0x00005555555d60a9 in x_produce_glyphs (it=0x7fffffff9b00) at xdisp.c:28294
>>
>> Here we're using xftfont_encode_char, even though we've just closed
>> the XFT font backend and should be using the X one for the minibuffer?
>> Is the 'it' there caching XFT information?
>>
>> I have no idea how to fix this. I can reproduce at will if more gdb
>> info is needed (BTW, emacs-26 has the same issue).
>>
>> Lisp Backtrace:
>> "message" (0xffffc458)
>> "desktop-read" (0xffffc7e0)
>> 0x563cec70 PVEC_COMPILED
>> "run-hooks" (0xffffcae0)
>> "command-line" (0xffffd388)
>> "normal-top-level" (0xffffd700)
>
> This looks like Bug#23386: Segfault when messing with font-backend.
It is in fact exactly that. I tried the patch there, it works for
me. How come it never went in?
Robert
next prev parent reply other threads:[~2019-02-08 14:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-08 12:09 switching font backends in .emacs.desktop causes crash Robert Pluim
2019-02-08 14:20 ` martin rudalics
2019-02-08 14:49 ` Robert Pluim [this message]
2019-02-08 15:54 ` martin rudalics
2019-02-08 16:14 ` Robert Pluim
2019-02-08 15:58 ` Eli Zaretskii
2019-02-08 16:16 ` Robert Pluim
2019-02-08 21:19 ` Eli Zaretskii
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=m28syqnxml.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=rudalics@gmx.at \
/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).