From: "Kazu Yamamoto" <kazu@iij.ad.jp>
To: eliz@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: EXC_BAD_ACCESS on Mac
Date: Thu, 04 Jul 2013 10:04:34 +0900 (JST) [thread overview]
Message-ID: <20130704.100434.997433713194426894.kazu@iij.ad.jp> (raw)
In-Reply-To: <8361wrbnyn.fsf@gnu.org>
Hi,
>> 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.
Are there any good ways to set watch point for this kind of local
variables?
--Kazu
next prev parent reply other threads:[~2013-07-04 1:04 UTC|newest]
Thread overview: 34+ 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 7:30 ` bug#14673: Fwd: " Matthias Meulien
2013-06-20 23:10 ` Juri Linkov
2013-07-03 23:05 ` 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
2013-07-03 16:36 ` Eli Zaretskii
2013-07-04 1:04 ` Kazu Yamamoto [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130704.100434.997433713194426894.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.