unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Kazu Yamamoto" <kazu@iij.ad.jp>
To: eliz@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: EXC_BAD_ACCESS on Mac
Date: Wed, 03 Jul 2013 23:19:11 +0900 (JST)	[thread overview]
Message-ID: <20130703.231911.312072594467070670.kazu@iij.ad.jp> (raw)
In-Reply-To: <83a9m3bwpj.fsf@gnu.org>

Hi,

>> 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:

	https://lists.gnu.org/archive/html/emacs-devel/2013-06/msg00554.html

I believe that all problems of mine are due to bad pointer values
broken by overflow or something.

--Kazu



  reply	other threads:[~2013-07-03 14:19 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
2013-07-03  4:36                           ` Kazu Yamamoto
2013-07-03 13:27                             ` Eli Zaretskii
2013-07-03 14:19                               ` Kazu Yamamoto [this message]
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=20130703.231911.312072594467070670.kazu@iij.ad.jp \
    --to=kazu@iij.ad.jp \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    /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).