From: Werner LEMBERG <wl@gnu.org>
To: eliz@gnu.org
Cc: 33885@debbugs.gnu.org
Subject: bug#33885: 27.0.50; PUA character makes emacs crash
Date: Fri, 28 Dec 2018 09:33:33 +0100 (CET) [thread overview]
Message-ID: <20181228.093333.165832196476716655.wl@gnu.org> (raw)
In-Reply-To: <2B70493D-734C-4773-AFD1-78E1DF7D7C61@gnu.org>
>> Loading the attached file `bug.el' (containing the single PUA
>> character U+E6A3) with
>>
>> emacs -Q bug.el
>>
>> causes a crash:
>>
>> xdisp.c:28955:
>> Emacs fatal error:
>> assertion failed:
>> it->ascent >= 0 && it->descent >= 0
>>
>> I've also attached the output of `bt full'.
>
> Do you have some custom font setup, which is supposed to display this
> PUA character?
No custom setup, but...
> Because on my system, there's no font for this codepoint (as I'd
> expect),
... a font that *does* have this character (following the MUFI
standard to display characters for medieval research).
https://folk.uib.no/hnooh/mufi/
The font in question is `Cardo Regular', Version 1.045, which you
can freely download as
http://scholarsfonts.net/cardo104.zip
(Note that the Google variant of this font doesn't contain the MUFI
characters.)
Character U+E6A3 gets mapped to glyph 3817, `uni00720325', which is
glyph `r' with a ring below; the `ttx' font disassembler shows the
following entry from the font's `glyf' table:
<TTGlyph name="uni00720325" xMin="52" yMin="-510" xMax="747" yMax="927">
<component glyphName="r" x="0" y="0" flags="0x204"/>
<component glyphName="ring" x="-39" y="-1589" flags="0x4"/>
</TTGlyph>
> and therefore Emacs displays it as "glyphless" character, showing a
> box with the character's code in hex, and that avoids the assertion
> violation.
>
> So please step through x_produce_glyphs when Emacs needs to produce
> a glyph for this character, and tell how you end up with both ascent
> and descent values zero. It isn't supposed to happen with valid
> fonts.
Uh, oh, I'm completely lost in this function; nowhere I can get
information on the font's name. Additionally, there is no repeatable
way to set a breakpoint right before the crash; the number of
iterations are different each time.
However, calling `strace' and searching for `open(' helped me identify
the last font that Emacs opened.
Werner
next prev parent reply other threads:[~2018-12-28 8:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-27 8:54 bug#33885: 27.0.50; PUA character makes emacs crash Werner LEMBERG
2018-12-27 10:36 ` Eli Zaretskii
2018-12-27 11:33 ` Eli Zaretskii
2018-12-28 8:33 ` Werner LEMBERG [this message]
2018-12-28 9:16 ` Eli Zaretskii
2018-12-28 12:38 ` Werner LEMBERG
2018-12-28 13:30 ` Eli Zaretskii
2018-12-28 14:58 ` Werner LEMBERG
2018-12-28 15:33 ` Eli Zaretskii
2018-12-28 17:03 ` Werner LEMBERG
2018-12-28 17:06 ` Werner LEMBERG
2018-12-28 19:15 ` Eli Zaretskii
2022-02-12 8:42 ` Lars Ingebrigtsen
2022-02-12 8:57 ` Eli Zaretskii
2022-03-12 22:43 ` Lars Ingebrigtsen
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=20181228.093333.165832196476716655.wl@gnu.org \
--to=wl@gnu.org \
--cc=33885@debbugs.gnu.org \
--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).