all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ken Raeburn <raeburn@permabit.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 18162 <18162@debbugs.gnu.org>
Subject: bug#18162: 24.3.92; segfault on null face pointer in face_for_char
Date: Fri, 1 Aug 2014 21:52:44 -0400	[thread overview]
Message-ID: <CAJJWxE_EbTincYStnxqPVcBXZAbvUXy4nhiahAbmxbMsR_hFMQ@mail.gmail.com> (raw)
In-Reply-To: <838un8sqeo.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 611 bytes --]

On Fri, Aug 1, 2014 at 1:57 AM, Eli Zaretskii <eliz@gnu.org> wrote:

> Sounds like some code called clear_face_cache, for some reason.  Is f
> at all the same frame where you were typing?  If not, the crash could
> have nothing to do with what you typed, but with some background
> activity on another frame.
>

I just ran Emacs a while under gdb, and it called clear_face_cache while I
wasn't doing anything interesting, just typing into a buffer. It happened
from in redisplay_internal when clear_face_cache_count reached 501. Its
documentation says it's used to "clear the face cache every once in a
while".

[-- Attachment #2: Type: text/html, Size: 959 bytes --]

  parent reply	other threads:[~2014-08-02  1:52 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 [this message]
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
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=CAJJWxE_EbTincYStnxqPVcBXZAbvUXy4nhiahAbmxbMsR_hFMQ@mail.gmail.com \
    --to=raeburn@permabit.com \
    --cc=18162@debbugs.gnu.org \
    --cc=eliz@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.