From: Eli Zaretskii <eliz@gnu.org>
To: "Kazu Yamamoto" <kazu@iij.ad.jp> (山本和彦)
Cc: emacs-devel@gnu.org
Subject: Re: EXC_BAD_ACCESS on Mac
Date: Tue, 25 Jun 2013 17:48:18 +0300 [thread overview]
Message-ID: <83mwqei6vh.fsf@gnu.org> (raw)
In-Reply-To: <20130625.132550.720238141888813764.kazu@iij.ad.jp>
> Date: Tue, 25 Jun 2013 13:25:50 +0900 (JST)
> From: Kazu Yamamoto (山本和彦) <kazu@iij.ad.jp>
>
> 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.
next prev parent reply other threads:[~2013-06-25 14:48 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-17 3:36 EXC_BAD_ACCESS on Mac Kazu Yamamoto
2013-06-17 15:03 ` Eli Zaretskii
2013-06-17 18:16 ` Kazu Yamamoto
2013-06-17 18:43 ` Eli Zaretskii
2013-06-17 19:37 ` Kazu Yamamoto
2013-06-17 19:48 ` Eli Zaretskii
2013-06-17 22:17 ` Kazu Yamamoto
2013-06-17 19:44 ` Kazu Yamamoto
2013-06-17 22:42 ` Paul Eggert
2013-06-18 0:29 ` Kazu Yamamoto
2013-06-18 2:27 ` Kazu Yamamoto
2013-06-18 2:45 ` Eli Zaretskii
2013-06-18 2:50 ` Kazu Yamamoto
2013-06-24 21:16 ` Jan Djärv
2013-06-25 1:30 ` Kazu Yamamoto
2013-06-18 17:20 ` Eli Zaretskii
2013-06-18 21:40 ` Kazu Yamamoto
2013-06-19 0:46 ` Show all lines in marked buffers matching a regexp (with patch) Matthias Meulien
2013-06-19 21:37 ` Juri Linkov
2013-06-20 1:29 ` EXC_BAD_ACCESS on Mac Kazu Yamamoto
2013-06-25 2:12 ` Kazu Yamamoto
2013-06-25 4:25 ` Kazu Yamamoto
2013-06-25 14:48 ` Eli Zaretskii [this message]
2013-07-03 4:36 ` Kazu Yamamoto
2013-07-03 13:27 ` Eli Zaretskii
2013-07-03 14:19 ` Kazu Yamamoto
2013-07-03 16:36 ` Eli Zaretskii
2013-07-04 1:04 ` Kazu Yamamoto
2013-07-04 16:06 ` Eli Zaretskii
2013-06-18 2:45 ` Eli Zaretskii
2013-06-18 2:48 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83mwqei6vh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=kazu@iij.ad.jp \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).