From: Eli Zaretskii <eliz@gnu.org>
To: Pip Cet <pipcet@gmail.com>
Cc: 21394@debbugs.gnu.org
Subject: bug#21394: 25.0.50; Segfault when displaying unprintable character in echo area while frames are being created
Date: Tue, 01 Sep 2015 19:57:19 +0300 [thread overview]
Message-ID: <83y4gqaxhs.fsf@gnu.org> (raw)
In-Reply-To: <CAOqdjBfJNqe7NZbLowznopsrAuzvSUfCFfgqWAA=Wd0HLkATdA@mail.gmail.com>
> Date: Tue, 1 Sep 2015 16:43:13 +0000
> From: Pip Cet <pipcet@gmail.com>
>
> Launch emacs -Q.
>
> C-x C-f emacs-bug-038.el
> M-x eval-buffer
>
> Wait for approximately one minute.
I waited for 1.5 minutes, and saw no crash. But that doesn't surprise
me, since these problems are very elusive.
> 26484 if (it->what == IT_CHARACTER)
> 26485 {
> 26486 XChar2b char2b;
> 26487 struct face *face = FACE_FROM_ID (it->f, it->face_id);
> 26488 struct font *font = face->font;
> 26489 struct font_metrics *pcm = NULL;
> 26490 int boff; /* Baseline offset. */
> 26491
> 26492 if (font == NULL)
> (gdb) p face
> $1 = (struct face *) 0x0
> (gdb) p it->face_id
> $2 = 18
> (gdb) p it->f->face_cache->used
> $3 = 15
This is another incarnation of several similar crashes we've seen for
the past year or so (you can see them on the bug tracker). I was
never able to find the code path which is responsible for this strange
situation, where a (supposedly) realized face is somehow not cached.
If you can somehow produce a trace of face caching and un-caching in
this recipe, with backtraces to show who calls those, perhaps we could
finally nail this sucker.
next prev parent reply other threads:[~2015-09-01 16:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-01 16:43 bug#21394: 25.0.50; Segfault when displaying unprintable character in echo area while frames are being created Pip Cet
2015-09-01 16:57 ` Eli Zaretskii [this message]
2015-09-01 17:30 ` Pip Cet
[not found] ` <CAOqdjBd7MN39Ra_3nnGCFQAb=xhv7AZt5f+rvAKqqYtoCQKTqQ@mail.gmail.com>
2015-09-01 18:08 ` Eli Zaretskii
2015-09-01 18:52 ` Pip Cet
2015-09-01 19:37 ` Eli Zaretskii
2015-09-01 20:19 ` Pip Cet
2015-09-02 15:16 ` Eli Zaretskii
2015-09-02 16:08 ` Pip Cet
2015-09-05 8:12 ` 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=83y4gqaxhs.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=21394@debbugs.gnu.org \
--cc=pipcet@gmail.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 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).