Re: EXC_BAD_ACCESS on Mac

[Eli Zaretskii]

> Date: Wed, 03 Jul 2013 13:36:28 +0900 (JST)
> Cc: address@hidden
> From: Kazu Yamamoto (山本和彦)
>  <address@hidden>
> 
> (gdb) p fontp
> $1 = (struct font *) 0x10f022d90
> (gdb) p fontp->driver
> $2 = (struct font_driver *) 0x10200303a
> (gdb) p fontp->driver->has_char
> $3 = (int (*)(Lisp_Object, int)) 0x88000000000000
>  
> > 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?
> 
> The stack trace is attached. 21843 is a part of my friend name. So, yes,
> this character was preparing in a buffer.
> 
> --Kazu
> 
> Program received signal EXC_BAD_ACCESS, Could not access memory.
> Reason: 13 at address: 0x0000000000000000
> 0x00000001002c351c in font_has_char (f=0x1146bc250, font=4546768277, c=21843) 
> at font.c:2938
> 2938        int result = fontp->driver->has_char (font, c);

Is 0x88000000000000 a valid address for a function?  If not, that's
the reason for the crash.  If it's a valid reason, I don't see why
this crashes, and some MacOS expert should take over this
investigation.