From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Michael Welsh Duggan Newsgroups: gmane.emacs.bugs Subject: bug#23522: 25.0.93; SEGFAULT when displaying HELLO Date: Fri, 13 May 2016 14:06:28 -0400 Message-ID: <87zirtal3v.fsf@md5i.com> References: <83lh3f9jdr.fsf@gnu.org> <83eg979g1p.fsf@gnu.org> <87wpmzgfxw.fsf@md5i.com> <8337pm9z8j.fsf@gnu.org> <877feyau34.fsf@md5i.com> <83k2iy7zxz.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1463162844 5803 80.91.229.3 (13 May 2016 18:07:24 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 13 May 2016 18:07:24 +0000 (UTC) Cc: Michael Welsh Duggan , 23522@debbugs.gnu.org, mwd@cert.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Fri May 13 20:07:13 2016 Return-path: Envelope-to: geb-bug-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 1b1HUV-0000Cr-Q9 for geb-bug-gnu-emacs@m.gmane.org; Fri, 13 May 2016 20:07:11 +0200 Original-Received: from localhost ([::1]:35502 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b1HUV-0004Kx-1V for geb-bug-gnu-emacs@m.gmane.org; Fri, 13 May 2016 14:07:11 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:53534) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b1HUQ-0004Ix-GF for bug-gnu-emacs@gnu.org; Fri, 13 May 2016 14:07:07 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1b1HUM-0003E2-CV for bug-gnu-emacs@gnu.org; Fri, 13 May 2016 14:07:06 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:37876) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b1HUM-0003Dx-8r for bug-gnu-emacs@gnu.org; Fri, 13 May 2016 14:07:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1b1HUM-000399-4V for bug-gnu-emacs@gnu.org; Fri, 13 May 2016 14:07:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Michael Welsh Duggan Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 13 May 2016 18:07:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 23522 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 23522-submit@debbugs.gnu.org id=B23522.146316279712059 (code B ref 23522); Fri, 13 May 2016 18:07:02 +0000 Original-Received: (at 23522) by debbugs.gnu.org; 13 May 2016 18:06:37 +0000 Original-Received: from localhost ([127.0.0.1]:50213 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1b1HTw-00038R-Pv for submit@debbugs.gnu.org; Fri, 13 May 2016 14:06:37 -0400 Original-Received: from md5i.com ([75.151.244.229]:55050) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1b1HTs-00038H-Ff for 23522@debbugs.gnu.org; Fri, 13 May 2016 14:06:36 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=md5i.com; s=dkim; h=Content-Type:MIME-Version:Message-ID:In-Reply-To:Date:References: Subject:Cc:To:From:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=AsYP7L6jBKZj6TawjNy8IAQnWLwmgMn920/ZR/SzLoE=; b=IVkdpCgLuIWzsFIcHGdiQvk9qL ooLnBycEZULTnNbfipBvirnG0KJissfUvAiGz4QzgyT3f6uEofghFSM5r0r96wlyolwfkcTbtQRlB k2oukI7H3QASY50KPCisGV8eJ; Original-Received: from md5i by md5i.com with local (Exim 4.87) (envelope-from ) id 1b1HTo-00047A-D8; Fri, 13 May 2016 14:06:28 -0400 In-Reply-To: <83k2iy7zxz.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 13 May 2016 18:14:16 +0300") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.92 (gnu/linux) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:118213 Archived-At: Eli Zaretskii writes: >> From: Michael Welsh Duggan >> Cc: mwd@md5i.com, Kenichi Handa , mwd@cert.org, >> 23522@debbugs.gnu.org >> Date: Fri, 13 May 2016 10:52:31 -0400 >> >> > So the question becomes: where did that value of 'to' come from, and >> > how come its value is bogus? Can you look at the code before the >> > faulting line and figure that out? >> >> It's being filled in by mflt_run() at ftfont.c:2646. > > Which means either a bug in the library or a bad font. That's my belief as well. >> >> xft:-unknown-FreeSerif-normal-normal-normal-*-15-*-*-*-*-0-iso10646-1 >> >> by these glyphs: >> >> [0 3 0 10195 9 0 10 10 0 nil] >> >> [0 3 2724 2103 10 1 10 10 1 nil] >> >> [0 3 2759 2132 0 -8 -2 13 -10 [-1 0 0]] >> > >> > So why does Emacs use FreeSerif on this system and Lohit Gujarati on >> > the faulting one? >> >> The two systems I have access to are running completely different >> distributions of Linux. I don't have much control over the packages >> installed on the system on which Emacs breaks. > > OK, but are both fonts installed on both systems? Not as far as I can determine. >> > Are both fonts installed on both systems? Is Lohit >> > Gujarati a bad font, by any chance? >> >> No idea. How can I find out? > > Install the latest version of it? Difficult in this instance. I'll see if it is possible. >> > Also, do both systems have the same version of libm17n-flt and m17n-db >> > libraries? >> >> Almost certainly not. > > Then perhaps using a newer version will help? > > Anyway, this sounds more and more like a bug in one of the libraries > Emacs uses, so I hope Handa-san will be able to chime in, since he is > one of the maintainers of those libraries. Quite possible. The most important thing, in my mind, is to prevent the crash if at all possible. That could be done either by writing code to catch this type of error, or by blacklisting in configure certain versions of the library (assuming that this is reasonable, or possible, or a real solution at all). -- Michael Welsh Duggan (md5i@md5i.com)