all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Clément Pit--Claudel" <clement.pitclaudel@live.com>
Cc: 24790@debbugs.gnu.org
Subject: bug#24790: Acknowledgement (Segmentation fault when changing default font on master)
Date: Tue, 25 Oct 2016 20:09:57 +0300	[thread overview]
Message-ID: <837f8wwe1m.fsf@gnu.org> (raw)
In-Reply-To: <8f8a8336-7e3f-27aa-9b66-6cbd313edb16@live.com> (message from Clément Pit--Claudel on Tue, 25 Oct 2016 12:05:35 -0400)

> From: Clément Pit--Claudel <clement.pitclaudel@live.com>
> Date: Tue, 25 Oct 2016 12:05:35 -0400
> 
> The issue seems to be that the font has self-intersecting glyphs; still, this shouldn't crash Emacs.

What do you mean by self-intersecting glyphs?

The backtrace you posted has nothing to do with drawing, AFAICT, it
happens inside internal-set-lisp-face-attribute, which attempts to
open a font, and dies inside AREF during that.

So I don't necessarily see how the glyphs could be related, at least
not with the data you provided.





  reply	other threads:[~2016-10-25 17:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-25 14:33 bug#24790: Segmentation fault when changing default font on master Clément Pit--Claudel
     [not found] ` <handler.24790.B.147740604715477.ack@debbugs.gnu.org>
2016-10-25 16:05   ` bug#24790: Acknowledgement (Segmentation fault when changing default font on master) Clément Pit--Claudel
2016-10-25 17:09     ` Eli Zaretskii [this message]
2016-10-25 17:50       ` Clément Pit--Claudel
2016-10-25 18:21         ` Eli Zaretskii
2016-10-25 19:31           ` Clément Pit--Claudel
2016-10-25 16:43 ` bug#24790: Segmentation fault when changing default font on master Eli Zaretskii
2016-10-25 19:27   ` Clément Pit--Claudel
2016-10-25 19:42     ` Eli Zaretskii
2016-10-25 20:18       ` Clément Pit--Claudel
2016-10-26 16:43         ` Glenn Morris

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=837f8wwe1m.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=24790@debbugs.gnu.org \
    --cc=clement.pitclaudel@live.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.