unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Antipov <dmantipov@yandex.ru>
To: npostavs@users.sourceforge.net,
	Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: 23386@debbugs.gnu.org
Subject: bug#23386: Segfault when messing with font-backend
Date: Sun, 10 Jul 2016 20:29:59 +0300	[thread overview]
Message-ID: <73cd86e5-3c92-cb6a-3a7b-1a5ec82c05de@yandex.ru> (raw)
In-Reply-To: <87d1mmiq35.fsf@users.sourceforge.net>

On 07/09/2016 10:11 PM, npostavs@users.sourceforge.net wrote:

> Here is a patch that attempts to fix the issue by resetting the font
> after the backend is changed.  It does let Emacs successfully open the
> frame with the new font (no funny box characters in the modeline), but
> I'm not sure if it's the best way of marking the font object invalid.

IMHO the original trick (request to drop font backend when there is a font
opened by using this backend) is practically meaningless, so why just not
prohibit it explicitly? For example, with:

diff --git a/src/frame.c b/src/frame.c
index 22143ab..d8f89ed 100644
--- a/src/frame.c
+++ b/src/frame.c
@@ -3708,7 +3708,19 @@ x_set_font_backend (struct frame *f, Lisp_Object new_value, Lisp_Object old_valu
      return;

    if (FRAME_FONT (f))
-    free_all_realized_faces (Qnil);
+    {
+      if (!NILP (new_value))
+	{
+	  Lisp_Object backend = FRAME_FONT (f)->props[FONT_TYPE_INDEX];
+
+	  /* Do not release the backend used by F's default font.  */
+	  if (NILP (Fmemq (backend, new_value)))
+	    error ("Font backend '%s' is in use by font '%s'",
+		   SDATA (SYMBOL_NAME (backend)),
+		   SDATA (FRAME_FONT (f)->props[FONT_NAME_INDEX]));
+	}
+      free_all_realized_faces (Qnil);
+    }

    new_value = font_update_drivers (f, NILP (new_value) ? Qt : new_value);
    if (NILP (new_value))

Dmitry





  parent reply	other threads:[~2016-07-10 17:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-27 13:13 bug#23386: Segfault when messing with font-backend Stefan Monnier
2016-04-27 14:02 ` Eli Zaretskii
2016-04-27 14:23   ` Stefan Monnier
2016-07-09 19:11     ` npostavs
2016-07-09 20:02       ` npostavs
2016-07-10 14:18         ` Eli Zaretskii
2016-07-10 20:15           ` npostavs
2016-07-10 17:29       ` Dmitry Antipov [this message]
2016-07-10 20:17         ` npostavs
2016-07-11 14:33           ` Eli Zaretskii
2016-07-12 15:20             ` Dmitry Antipov
2016-07-12 17:45               ` Eli Zaretskii
2016-07-12 17:58                 ` Dmitry Antipov

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=73cd86e5-3c92-cb6a-3a7b-1a5ec82c05de@yandex.ru \
    --to=dmantipov@yandex.ru \
    --cc=23386@debbugs.gnu.org \
    --cc=monnier@IRO.UMontreal.CA \
    --cc=npostavs@users.sourceforge.net \
    /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).