GNU bug report logs - #23386
Segfault when messing with font-backend

Previous Next

Package: emacs;

Reported by: Stefan Monnier <monnier <at> IRO.UMontreal.CA>

Date: Wed, 27 Apr 2016 13:14:01 UTC

Severity: normal

Tags: confirmed

Merged with 35803, 36835, 39865

Found in versions 25.0.95, 28.0.50, 25.0.50, 24.1, 24.5, 26.2, 27.0.50

Fixed in version 27.1

Done: Robert Pluim <rpluim <at> gmail.com>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: npostavs <at> users.sourceforge.net
Cc: monnier <at> IRO.UMontreal.CA, 23386 <at> debbugs.gnu.org
Subject: bug#23386: Segfault when messing with font-backend
Date: Sun, 10 Jul 2016 17:18:02 +0300
> From: npostavs <at> users.sourceforge.net
> Cc: 23386 <at> debbugs.gnu.org,  Eli Zaretskii <eliz <at> gnu.org>
> Date: Sat, 09 Jul 2016 16:02:30 -0400
> 
> > 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.
> 
> Definitely not the best way: it causes segfault on delete-frame.

Backtrace from that segfault?

I think one idea that could be useful is to trace the creation of
relevant objects when Emacs starts up, starting with the call to
font_update_drivers, and then compare that with what happens in this
case.  That could delineate the missing parts and the differences
which could point the way to solving this cleanly.

Thanks.




This bug report was last modified 5 years and 64 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.