From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: 30874@debbugs.gnu.org, jsynacek@redhat.com
Subject: bug#30874: 27.0.50; Emacs crashes
Date: Mon, 26 Mar 2018 20:33:21 +0300 [thread overview]
Message-ID: <83605ig2se.fsf@gnu.org> (raw)
In-Reply-To: <87o9ja230e.fsf@gmail.com> (message from Robert Pluim on Mon, 26 Mar 2018 18:52:17 +0200)
> From: Robert Pluim <rpluim@gmail.com>
> Cc: 30874@debbugs.gnu.org, jsynacek@redhat.com
> Date: Mon, 26 Mar 2018 18:52:17 +0200
>
> > But now that I actually see it, I don't think I understand the reason:
> > the call to XftTextExtents8 asks the xft font back-end to produce the
> > extents for an all-ASCII string, so the fact that it may not have
> > glyphs for some exotic non-ASCII characters couldn't be the culprit.
>
> OK. Is it possible that because we're in synchronous mode that the
> signal has been received just at an inopportune moment?
I doubt that: the backtrace looks very much like describing the actual
call into the X libraries.
> It doesn't crash if I do eg (insert-char ?a), nor (insert-char #x700).
As expected. But if you put a breakpoint at line 378 of xftfont.c, do
you see the same call to XftTextExtents8 with the same arguments in
the case of 'a'?
> > Can you figure out what's going on here, and why?
>
> Looks like I'll have to go poking around in the guts of Xft. Pointers
> appreciated.
Sorry, I don't know enough about the xftfont back-end to provide any
pointers. Maybe someone else here would.
next prev parent reply other threads:[~2018-03-26 17:33 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 10:24 bug#30874: 27.0.50; Emacs crashes Jan Synacek
2018-03-20 12:04 ` Eli Zaretskii
2018-03-20 12:12 ` Jan Synacek
2018-03-20 12:44 ` Eli Zaretskii
2018-03-22 12:28 ` Jan Synacek
2018-03-22 13:01 ` Eli Zaretskii
2018-03-22 13:05 ` Jan Synacek
2018-03-22 14:55 ` Eli Zaretskii
2018-03-26 9:12 ` Jan Synacek
2018-03-26 10:33 ` Robert Pluim
2018-03-26 15:25 ` Eli Zaretskii
2018-03-26 16:52 ` Robert Pluim
2018-03-26 17:33 ` Eli Zaretskii [this message]
2018-03-26 20:17 ` Robert Pluim
2018-03-26 22:16 ` Robert Pluim
2018-03-27 3:02 ` Eli Zaretskii
2018-03-27 8:57 ` Robert Pluim
2018-03-29 10:25 ` Eli Zaretskii
2018-03-29 16:14 ` Robert Pluim
2018-03-29 17:07 ` Eli Zaretskii
2018-03-30 5:10 ` Glenn Morris
2018-03-30 8:00 ` Eli Zaretskii
2018-03-30 10:36 ` Robert Pluim
2018-03-30 11:46 ` Eli Zaretskii
2018-03-30 13:00 ` Robert Pluim
2018-03-30 13:46 ` Eli Zaretskii
2018-03-31 13:55 ` Robert Pluim
2018-03-31 14:59 ` Eli Zaretskii
2018-04-03 9:24 ` Robert Pluim
2018-04-03 8:00 ` Jan Synacek
2018-04-03 9:22 ` Robert Pluim
2018-04-03 9:42 ` Eli Zaretskii
2018-04-03 12:52 ` Robert Pluim
2018-03-29 10:35 ` Jan Synacek
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=83605ig2se.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=30874@debbugs.gnu.org \
--cc=jsynacek@redhat.com \
--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).