From: Eli Zaretskii <eliz@gnu.org>
To: Alan Third <alan@idiocy.org>
Cc: 22818@debbugs.gnu.org, josh@berdine.net
Subject: bug#22818: 25.1.1 Emacs.app crash ns_compute_glyph_string_overhangs
Date: Sat, 19 Nov 2016 20:12:07 +0200 [thread overview]
Message-ID: <83bmxbbaq0.fsf@gnu.org> (raw)
In-Reply-To: <20161119155112.GB591@breton.holly.idiocy.org> (message from Alan Third on Sat, 19 Nov 2016 15:51:12 +0000)
> Date: Sat, 19 Nov 2016 15:51:12 +0000
> From: Alan Third <alan@idiocy.org>
> Cc: josh@berdine.net, 22818@debbugs.gnu.org
>
> (gdb) p s->face.id
> $1 = 17
> (gdb) p lface_id_to_name[17]
> $2 = 31008
> (gdb) xsymbol
> $3 = (struct Lisp_Symbol *) 0x7ab8
> Cannot access memory at address 0x7ac0
> (gdb)
So I guess that face was freed or otherwise made invalid. I thought
we've got rid of these problems, sigh...
If you start "emacs -Q", let Emacs start up, and then look at that
face ID, do you see a valid symbol? IOW, do this:
$ gdb ./emacs
...
(gdb) break Fredraw_display
(gdb) r -Q
Then, after Emacs starts up, type "M-x redraw-display RET", and at the
GDB prompt type:
(gdb) p lface_id_to_name[17]
(gdb) xsymbol
What does that show?
And what is the value of next_lface_id at that point?
next prev parent reply other threads:[~2016-11-19 18:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 13:41 bug#22818: 25.0.91; nextstep/Emacs.app Crash ns_compute_glyph_string_overhangs Aaron S. Hawley
2016-05-18 20:07 ` Alan Third
2016-05-18 21:09 ` Aaron S. Hawley
2016-11-18 21:31 ` bug#22818: 25.1.1 Emacs.app crash ns_compute_glyph_string_overhangs Josh Berdine
2016-11-19 7:07 ` Eli Zaretskii
2016-11-19 10:07 ` Alan Third
2016-11-19 10:27 ` Eli Zaretskii
2016-11-19 11:18 ` Alan Third
2016-11-19 11:43 ` Eli Zaretskii
2016-11-19 14:53 ` Alan Third
2016-11-19 15:09 ` Eli Zaretskii
2016-11-19 15:51 ` Alan Third
2016-11-19 18:12 ` Eli Zaretskii [this message]
2016-11-19 19:05 ` Alan Third
2016-11-19 19:27 ` Eli Zaretskii
2016-11-19 19:38 ` Alan Third
2022-04-18 11:32 ` bug#22818: 25.0.91; nextstep/Emacs.app Crash ns_compute_glyph_string_overhangs Lars Ingebrigtsen
2022-04-18 11:44 ` Aaron S. Hawley
2022-04-18 11:45 ` Lars Ingebrigtsen
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=83bmxbbaq0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=22818@debbugs.gnu.org \
--cc=alan@idiocy.org \
--cc=josh@berdine.net \
/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).