Re: EXC_BAD_ACCESS on Mac

[Eli Zaretskii]

> Date: Tue, 25 Jun 2013 13:25:50 +0900 (JST)
> From: Kazu Yamamoto (山本和彦) <address@hidden>
> 
> 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.