[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: EXC_BAD_ACCESS on Mac
From: |
Eli Zaretskii |
Subject: |
Re: EXC_BAD_ACCESS on Mac |
Date: |
Wed, 03 Jul 2013 19:36:00 +0300 |
> Date: Wed, 03 Jul 2013 23:19:11 +0900 (JST)
> Cc: address@hidden
> From: Kazu Yamamoto (山本和彦)
> <address@hidden>
>
> >> 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.
>
> I think that 0x88000000000000 is a bad pointer value as I said
> previously:
Then perhaps a way to catch the bug is to run Emacs under GDB, and set
a watchpoint on fontp->driver->has_char.