From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.help Subject: Re: Seek advice about crashes dealing with fonts/faces Date: Thu, 09 Apr 2015 10:19:29 +0300 Message-ID: <83k2xlg45a.fsf@gnu.org> References: NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1428564010 11597 80.91.229.3 (9 Apr 2015 07:20:10 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 9 Apr 2015 07:20:10 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Thu Apr 09 09:20:02 2015 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Yg6kr-00082g-K3 for geh-help-gnu-emacs@m.gmane.org; Thu, 09 Apr 2015 09:20:01 +0200 Original-Received: from localhost ([::1]:56553 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yg6kq-0003dE-PS for geh-help-gnu-emacs@m.gmane.org; Thu, 09 Apr 2015 03:20:00 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:56795) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yg6kf-0003ck-Hl for help-gnu-emacs@gnu.org; Thu, 09 Apr 2015 03:19:50 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Yg6kb-0008MV-HT for help-gnu-emacs@gnu.org; Thu, 09 Apr 2015 03:19:49 -0400 Original-Received: from mtaout20.012.net.il ([80.179.55.166]:46288) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yg6kb-0008MA-90 for help-gnu-emacs@gnu.org; Thu, 09 Apr 2015 03:19:45 -0400 Original-Received: from conversion-daemon.a-mtaout20.012.net.il by a-mtaout20.012.net.il (HyperSendmail v2007.08) id <0NMJ00K002PL3400@a-mtaout20.012.net.il> for help-gnu-emacs@gnu.org; Thu, 09 Apr 2015 10:19:16 +0300 (IDT) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout20.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NMJ00KAR3043Z00@a-mtaout20.012.net.il> for help-gnu-emacs@gnu.org; Thu, 09 Apr 2015 10:19:16 +0300 (IDT) In-reply-to: X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: Solaris 10 X-Received-From: 80.179.55.166 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:103598 Archived-At: > From: "Ludwig, Mark" > Date: Wed, 8 Apr 2015 22:19:40 +0000 > > I've had Emacs 24.4 crash a couple of times this week, and > wonder if anyone else has seen anything like this or has > advice about how to make an actionable bug report. > > Emacs is running on Solaris, with the X display pointing to > eXceed (i.e., Windoze). > > Both of the core dumps have the same 8 functions leading up > to a bus error (SIGBUS): > > FcPatternObjectFindElt (causes/triggers the SIGBUS) > FcFontSetList > FcFontList > ftfont_list > xftfont_list > font_list_entities > font_find_for_lface > font_load_for_lface > > Two different functions call font_load_for_lface in my two > core files, and the rest of the calls are quite different. > > I can't reproduce this at will, but I have a feeling it will > recur. Any advice about how to catch it or get better > diagnostic information for a bug report? Run Emacs under GDB, and when it crashes, show the full backtrace. Also, try to figure out which variable is triggering SIGBUS, and show that as well. It is best to build Emacs without optimizations and with -g3 command-line switch to the compiler (or its equivalent, if you don't use GCC), since the backtrace and the other debug info is much more reliable then. > Do I already have enough for an actionable bug report? You do, but adding the information mentioned above would make the report much more useful. SIGBUS actually sounds like a fontconfig bug, so if there's a newer version of that library, perhaps try using it. Or maybe look for similar problems in fontconfig bug database, if there is such a thing.