all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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 21:08:57 +0300	[thread overview]
Message-ID: <83twreau6e.fsf@gnu.org> (raw)
In-Reply-To: <CAOqdjBd7MN39Ra_3nnGCFQAb=xhv7AZt5f+rvAKqqYtoCQKTqQ@mail.gmail.com>

> Date: Tue, 1 Sep 2015 17:33:10 +0000
> From: Pip Cet <pipcet@gmail.com>
> 
> This is the full log, including all my backspacing (so the end might be more
> readable in the edited log I've sent to the list). I'm not sure what the size
> limits are for sending attachments to the list.
> [...]
> (gdb) p face
> $1787 = (struct face *) 0x0
> (gdb) p it
> $1788 = (struct it *) 0x7fffffff9de0
> (gdb) p it->face_id
> $1789 = 18
> $1790 = (struct frame *) 0x129f9e0
> (gdb) p it->f->face_cache->used
> $1791 = 15

I see the problematic face always has face ID of 18, and the 'used'
field is always 15 when the segfault strikes.  So I guess the next
step is to make the breakpoint in cache_face conditional on i being
18, and then see whether c->used is set to 19 during that call to
cache_face.  If it does, then a watchpoint (by location) on c->used
should show which code makes the value smaller.





  parent reply	other threads:[~2015-09-01 18:08 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
2015-09-01 17:30   ` Pip Cet
     [not found]     ` <CAOqdjBd7MN39Ra_3nnGCFQAb=xhv7AZt5f+rvAKqqYtoCQKTqQ@mail.gmail.com>
2015-09-01 18:08       ` Eli Zaretskii [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83twreau6e.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 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.