From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: EXC_BAD_ACCESS on Mac Date: Tue, 25 Jun 2013 17:48:18 +0300 Message-ID: <83mwqei6vh.fsf@gnu.org> References: <20130619.064010.988324446963344956.kazu@iij.ad.jp> <20130620.102915.1011832207076735259.kazu@iij.ad.jp> <20130625.111215.438859328778697109.kazu@iij.ad.jp> <20130625.132550.720238141888813764.kazu@iij.ad.jp> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1372171735 9510 80.91.229.3 (25 Jun 2013 14:48:55 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 25 Jun 2013 14:48:55 +0000 (UTC) Cc: emacs-devel@gnu.org To: Kazu Yamamoto (=?iso-2022-jp?B?GyRCOzNLXE9CSScbKEI=?=) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jun 25 16:48:55 2013 Return-path: Envelope-to: ged-emacs-devel@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 1UrUYB-0003WN-EO for ged-emacs-devel@m.gmane.org; Tue, 25 Jun 2013 16:48:55 +0200 Original-Received: from localhost ([::1]:49531 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UrUYB-0003AF-4A for ged-emacs-devel@m.gmane.org; Tue, 25 Jun 2013 10:48:55 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:43743) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UrUY7-0003A0-Nh for emacs-devel@gnu.org; Tue, 25 Jun 2013 10:48:53 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UrUY2-0006dt-RN for emacs-devel@gnu.org; Tue, 25 Jun 2013 10:48:51 -0400 Original-Received: from mtaout22.012.net.il ([80.179.55.172]:55819) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UrUY2-0006dY-JI for emacs-devel@gnu.org; Tue, 25 Jun 2013 10:48:46 -0400 Original-Received: from conversion-daemon.a-mtaout22.012.net.il by a-mtaout22.012.net.il (HyperSendmail v2007.08) id <0MOY00I00EFI7600@a-mtaout22.012.net.il> for emacs-devel@gnu.org; Tue, 25 Jun 2013 17:48:28 +0300 (IDT) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout22.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0MOY00HOEEGRJ9C0@a-mtaout22.012.net.il>; Tue, 25 Jun 2013 17:48:27 +0300 (IDT) In-reply-to: <20130625.132550.720238141888813764.kazu@iij.ad.jp> X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: Solaris 10 X-Received-From: 80.179.55.172 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:161027 Archived-At: > Date: Tue, 25 Jun 2013 13:25:50 +0900 (JST) > From: Kazu Yamamoto (山本和彦) > > Here is yet another catch today: > > Program received signal EXC_BAD_ACCESS, Could not access memory. > Reason: 13 at address: 0x0000000000000000 > 0x00000001002c1f0c in font_has_char (f=0x1070261b8, font=4417553805, c=38761) at font.c:2938 > 2938 int result = fontp->driver->has_char (font, c); > (gdb) info stack > #0 0x00000001002c1f0c in font_has_char (f=0x1070261b8, font=4417553805, c=38761) at font.c:2938 > #1 0x0000000100382b4e in fontset_find_font (fontset=4340278349, c=38761, face=0x1056dca20, id=54, fallback=false) at fontset.c:665 > #2 0x00000001003832ae in fontset_font (fontset=4414099629, c=38761, face=0x1056dca20, id=54) at fontset.c:759 > #3 0x0000000100383b1e in face_for_char (f=0x1070261b8, face=0x1056dca20, c=38761, pos=46746, object=4328534074) at fontset.c:971 > #4 0x0000000100048ee7 in get_next_display_element (it=0x7fff5fbf9db8) at xdisp.c:6956 Please show for frame #0 the values of the following variables: fontp fontp->driver fontp->driver->has_char Also, the value of the character C that was passed to font_has_char is 38761 or 0x9769 in hex. This is the codepoint of the character 革. Is it reasonable to expect such a character to come up in the context of whatever you were reading/editing at the time of the crash? Or is the character codepoint also suspect as garbled? Thanks.