From: Eli Zaretskii <eliz@gnu.org>
To: raeburn@permabit.com
Cc: 18162@debbugs.gnu.org
Subject: bug#18162: 24.3.92; segfault on null face pointer in face_for_char
Date: Sat, 02 Aug 2014 15:50:48 +0300 [thread overview]
Message-ID: <83iombqclz.fsf@gnu.org> (raw)
In-Reply-To: <83mwbnqilz.fsf@gnu.org>
> Date: Sat, 02 Aug 2014 13:41:12 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 18162@debbugs.gnu.org
>
> > From: Ken Raeburn <raeburn@permabit.com>
> > Date: Sat, 2 Aug 2014 06:00:34 -0400
> > Cc: 18162@debbugs.gnu.org
> >
> > emacs -Q
> > M-x list-faces-display RET
> > Type into the scratch buffer:
> > (progn (clear-face-cache t) (internal-char-font nil 8230))
> > Hit C-j to evaluate. This generally works the first time. Move the cursor back up to the end of the expression and hit C-j again. The second time usually crashes for me.
>
> It didn't crash for me.
Moreover, even if I force the call to clear_font_cache by invoking
clear-font-cache in the progn, I don't see a crash, and the use count
of the frame's face cache is not zero.
So one way of tracking this down would be to put a breakpoint in
Fclear_face_cache, and when it breaks, step through the function until
it assigns the frame pointer to 'f', and put a watchpoint on
f->face_cache->used, to see which code zeroes it. My guess would be
that some code calls free_realized_faces (I misremembered earlier:
clear_face_cache doesn't do that).
next prev parent reply other threads:[~2014-08-02 12:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-31 23:24 bug#18162: 24.3.92; segfault on null face pointer in face_for_char Ken Raeburn
2014-08-01 5:57 ` Eli Zaretskii
2014-08-01 8:46 ` Ken Raeburn
2014-08-02 1:52 ` Ken Raeburn
2014-08-02 6:49 ` Eli Zaretskii
2014-08-02 10:00 ` Ken Raeburn
2014-08-02 10:41 ` Eli Zaretskii
2014-08-02 12:50 ` Eli Zaretskii [this message]
2014-08-03 6:51 ` Ken Raeburn
2014-08-03 15:04 ` Eli Zaretskii
2014-08-07 4:12 ` Ken Raeburn
2014-08-07 15:19 ` 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=83iombqclz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=18162@debbugs.gnu.org \
--cc=raeburn@permabit.com \
/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.