all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dmitry Antipov <dmantipov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>, Stephen Berman <stephen.berman@gmx.net>
Cc: 17771@debbugs.gnu.org
Subject: bug#17771: 24.3.91; SIGSEGV in cleanup_vector
Date: Mon, 16 Jun 2014 12:02:21 +0400	[thread overview]
Message-ID: <539EA48D.4050802@yandex.ru> (raw)
In-Reply-To: <83fvj8x3o9.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 358 bytes --]

On 06/13/2014 06:52 PM, Eli Zaretskii wrote:

> So Dmitry, I think Stephen here just found you a perfect recipe to
> reproduce bug #16140, something that I failed to do.  Could you please
> look into this?

Reproduced. My machine looks much faster so I'm not sure it's always
possible to hit C-g in time; anyway, this simple fix just works for me.

Dmitry



[-- Attachment #2: bug17771.patch --]
[-- Type: text/x-patch, Size: 617 bytes --]

=== modified file 'src/font.c'
--- src/font.c	2014-06-10 03:32:36 +0000
+++ src/font.c	2014-06-16 07:55:14 +0000
@@ -158,6 +158,7 @@
   Lisp_Object tail, frame;
   struct font_driver_list *fdl;
 
+  eassert (drv);
   for (fdl = font_driver_list; fdl; fdl = fdl->next)
     if (fdl->driver == drv)
       return true;
@@ -219,6 +220,9 @@
     }
   if (size > 0)
     font->props[FONT_SIZE_INDEX] = make_number (pixelsize);
+  /* NULL means that this font is not allocated by any driver yet,
+     and GC may be called before the driver is assigned (#Bug17771).  */
+  font->driver = NULL;
   return font_object;
 }
 


  reply	other threads:[~2014-06-16  8:02 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-13  9:12 bug#17771: 24.3.91; SIGSEGV in cleanup_vector Stephen Berman
2014-06-13  9:41 ` Eli Zaretskii
2014-06-13  9:50   ` Stephen Berman
2014-06-13 12:19     ` Eli Zaretskii
2014-06-13 12:39       ` Stephen Berman
2014-06-13 13:28         ` Eli Zaretskii
2014-06-13 13:34           ` Stephen Berman
2014-06-13 13:44             ` Eli Zaretskii
2014-06-13 13:53               ` Stephen Berman
2014-06-13 13:58                 ` Eli Zaretskii
2014-06-13 14:13                   ` Stephen Berman
2014-06-13 14:52                     ` Eli Zaretskii
2014-06-16  8:02                       ` Dmitry Antipov [this message]
2014-06-16 10:16                         ` Stephen Berman
2014-06-16 12:37                           ` Dmitry Antipov
2014-06-16 13:07                             ` Stephen Berman
2014-06-16 13:19                               ` Dmitry Antipov
2014-06-16 13:32                                 ` Andreas Schwab
2014-06-16 15:49                                   ` Stephen Berman
2014-06-16 16:21                                     ` Dmitry Antipov
2014-06-16 21:34                                       ` Stephen Berman
2014-06-17  2:25                                         ` Dmitry Antipov
2014-06-17 13:40                                           ` Stephen Berman
2014-06-18 12:54                                   ` Wolfgang Jenkner
2014-06-18 13:50                                     ` Stephen Berman
2014-06-18 14:01                                       ` Dmitry Antipov
2014-06-18 16:00                                         ` Stephen Berman
2014-06-18 16:24                                           ` Dmitry Antipov
2014-06-18 17:00                                             ` Stephen Berman
2014-08-12  3:59                                               ` Glenn Morris
2014-06-16 15:49                                 ` Stephen Berman
2014-06-16 16:03                                   ` Dmitry Antipov
2014-06-16 21:33                                     ` Stephen Berman
2014-06-17  2:09                                       ` Dmitry Antipov
2014-06-17 13:41                                         ` Stephen Berman
2014-06-17 18:11                                           ` Dmitry Antipov
2014-06-18 13:50                                             ` Stephen Berman

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=539EA48D.4050802@yandex.ru \
    --to=dmantipov@yandex.ru \
    --cc=17771@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=stephen.berman@gmx.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 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.